Architecture Boundary

Architecture Boundary

Responsibility Map

• README.md and docs/: public reviewer contract and project orientation
• scripts/: CLI entrypoints and governance workflow implementation
• policies/: policy source used by generated agent shims
• registry/skills/: reusable skill instructions for engineering workflows
• templates/shims/: generated shim contract and template material
• tests/: public validation seam for the sanitized preview
• GitHub remote: publication boundary and CI readback

Dependency Direction

The preview repository is self-contained. Runtime and documentation must not depend on:

• the private source checkout
• source Git history
• private issue or pull request state
• local machine paths
• local task cache files

The preview may describe the governance model, but public validation must run from the preview checkout itself.

Test Seam

The public smoke tests validate that:

• the CLI help command runs
• required reviewer-facing files exist
• private artifact directories are absent
• common long credential-like token forms are not present in tracked text files

Scope Map

• Selection: public-safe scripts, policies, registry skills, templates, docs, tests
• Sanitization: removal or rewriting of source repo URLs, local paths, private evidence markers, and generated artifacts
• Validation: local pytest, whitespace check, targeted sensitive-string scans, and GitHub Actions
• Publication: clean initial commit pushed to the private preview repository

Residual Risk

The public preview is intentionally narrow. It contains smoke tests rather than the full private operational test corpus. Future public hardening can add broader behavioral tests after any private-only fixtures are replaced with public fixtures.