Repo-specific architecture-doc overlay for therefore. Apply this on top of the global `staff-software-architect` skill when updating therefore’s engineering blueprint and architecture docs to reflect a feature PR or refactor (responsibilities, key flows, invariants, testing notes). Use when changes introduce new modules, data flows, persistence, sync, permissions/capabilities, or boundary shifts, especially for edits under `docs/ENGINEERING_BLUEPRINT.md`, `docs/architecture/`, or `docs/technical/` (or when doing an architecture doc audit to reduce drift). Not for general docs cleanup; use `docs-curator` for dedupe/navigation work.
Operate for a solo builder, not a multi-team org.
Apply the global staff-software-architect skill first for the structural judgment. This skill is the therefore-specific overlay that maps that judgment onto the canonical architecture docs, doc map, and output contract in this repo.
Keep architecture guidance accurate so future work is faster and safer.
references/therefore-doc-map.md to choose the right canonical docs for the change.
docs/guidelines/development-philosophy.md for product truths, architecture rules, and complexity triggers that inform structural decisions.docs/ENGINEERING_BLUEPRINT.md, preserve its tone: practical, constraint-driven, focused on responsibilities and risks.Summary:
Scope:
Checks performed:
Findings:
Recommendations:
Verification:
Provide the doc edits (patch) plus the summary in the output format above.