Context Packaging

Configs and context that travel must arrive safe, reproducible, and actually usable. Redact first, generate (never hand-maintain), version everything.

When to use

• Exporting agent configs (guidelines, registries, skills, plugins) for another machine or agent.
• Handoff dossiers (enabling a new agent in one read).
• Backups of working context.

Method

1. Scope declaration first: what travels (config/rules/skills/state summaries/dossiers), to whom, and why — write it down; the pack inherits this boundary.
2. Redaction before anything: keys → environment references; personal data minimized (purpose-limited); contacts/financials excluded by default; run secret scanners + a manual pass; assume the receiver's storage is less protected than yours.
3. Structure: manifest (contents, version, date, generator), stable folder layout, README/runbook for the receiving agent; machine-readable where possible.
4. Reproducibility: exports are generated by a script from the source of truth — never hand-assembled; versioned in git; signed (secure-build-pattern) so authenticity is checkable.
5. Handoff dossiers: goals, current state, open loops, contact/protocol rules, first tasks — the milotojack pattern; date everything; avoid stale claims (mark review date).
6. Freshness: expiry/review dates; stale packs flagged; single upstream source (export = derived, never the primary).
7. Privacy: private repos; access-limited; complies with contact-handling rules; no third-party personal data without a lawful basis.

Quality gates

• Redaction scan clean (automated + manual).
• Manifest + version + date present; export reproducible by script.
• Receiver runbook tested (fresh agent can operate from the pack).
• Pack signed; stored privately.

Red lines

• Never export secrets or PII unredacted; never hand-maintain a derived pack silently; every pack carries date + source.

Related

skill-ops · secrets-management · technical-writing · privacy-compliance.