Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
c0c7690724
Move the 8 directories under bundles/ to the repo root via git mv and remove the now-empty bundles/ directory. Replace the "bundles" entry in pyproject.toml [tool.deptry] extend_exclude with the 8 moved dir names so the moved trees stay excluded from Python dependency analysis. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
1.8 KiB
Communication
Communication keeps an embedded engagement moving without hiding uncertainty. Use short records with explicit labels rather than a narrative that blends fact and promise.
Status update
- Outcome: what changed in the target workflow or decision.
- Evidence: source fact or engagement observation, with artifact and date.
- Inference: what the evidence may mean, including confidence and unknowns.
- Decision needed: the smallest authorized choice, by whom, and by when.
- Commitment: owner, deliverable, due date, and dependency.
- Stop/escalation: what is blocked and what safe work can continue.
Handoff
State the receiving owner, purpose, current stage, entry evidence, artifacts, known limitations, unresolved risks, authority boundary, acceptance condition, and requested response. A handoff is not complete when a link is sent; the receiver must accept ownership or explicitly reject the boundary.
Field learning
Report what was observed, what was tried, what changed, what failed, what may generalize, and what should not be generalized. Label recommendations as recommendations until the receiving authority records a decision. Avoid naming private customers, hosts, paths, or deployment details in reusable public artifacts.
External-sharing gate
Treat every engagement artifact as private by default. Before any artifact leaves the authorized engagement context, name the receiving audience and have an accountable reviewer remove or generalize customer and stakeholder names, people, hosts, paths, credentials, identifiers, sensitive workflow details, security posture, commercial terms, and other context-specific information. Record the artifact's sharing classification, reviewer, and review date. A reusable lesson may be shared only after this gate; compliance or stakeholder urgency does not waive it.