PROFESSIONAL PRACTICE AND COLLABORATION

EXAMPLES Example 1: Cross-team sign-off. A harness engineer proposing a new agent capability gets approval from the governance team on its permission scope and from the observability team on its new tracing data before writing code. Example 2: A design document. A short document explains why a new retry strategy was chosen over three alternatives, so future engineers understand the reasoning and not just the final code. Example 3: Sharing lessons. A weekly post summarizing what was learned from the week's incidents keeps the whole organization current without everyone reading every postmortem. Example 4: A fixed reading routine. A harness engineer keeps a short reading list of framework changelogs, protocol updates, and security advisories, reviewed every week on a fixed schedule. PRACTICE LAB CONNECTION Write a design-decision document for one real choice made in your Resume Review Agent lab. Good candidates are the compaction threshold of six thousand estimated tokens, the repeated-call limit of three, the choice to remove suspected instructions instead of only labeling them, or the choice to give the writer only a slim dictionary. Then test the prompts below against your document.