architecture-compass

Architecture Compass

Goal

Make architecture decisions explicit, binding, locally traceable, and executable. Establish repository-native governance, audit implementation, or perform an ADR-guided refactor without overwriting accepted history or broadening authority.

When to use

• Establish/reconcile ADR governance or audit architecture, decision coverage, drift, risk, and evidence.
• Plan or execute bounded ADR-governed work, including broad work that first requires durable decisions.

When not to use

• Tiny/style-only or ordinary governed edits with no architecture consequence or ADR-aware boundary check.
• Generic framework education or requests without target evidence and a governance, audit, planning, or refactoring outcome.

Activation and receipt presentation

Route activation and receipt presentation through AC-ADR-053 Short · Long · Guide. Start with Short and load Long before conditionally loading AC-INTERNAL-002 from the internal index for renderer-selection mechanics. This dispatcher does not define a presentation profile or renderer policy.

Workflow selection

Every direct invocation exposes exactly these public workflows:

• setup: establish or reconcile repository-native ADR governance with recommended or complete coverage.
• audit: perform a strictly read-only architecture, ADR-coverage, drift, and validation assessment.
• refactor: execute explicit bounded work already governed by accepted local ADRs.
• plan-refactor: collaborate on and persist an approved bounded refactoring specification without implementing it.
• plan-run-refactor: plan, persist, recheck, and execute an approved broad or decision-bearing refactor.

Begin activation with a compact line exposing setup | audit | refactor | plan-refactor | plan-run-refactor, then name the selected route, rationale and authorized scope. Keep this disclosure in response-only assessments too; a short answer still exposes all five choices.

There is no auto workflow. Route by task evidence:

Intent evidence	Selected workflow
Establish or reconcile ADR governance	setup/recommended
Review architecture, ADR coverage, drift, or risk	audit
Produce a refactoring plan without execution	plan-refactor
Broad implementation or unresolved durable decisions before execution	plan-run-refactor
Explicit bounded work fully governed by accepted local ADRs	refactor

For clear direct or agent-discovered intent with sufficient authority, state the complete workflow set, selected workflow and rationale compactly, then proceed. Name write scope and any material capability, protected-state, or separate approval boundary; put detailed evidence in the matching receipt. A bare activation, conflicting cues, or ambiguity about outcome, governance, scope, persistence, or mutation authority requires showing the workflows and asking.

Agent-initiated activation may select and announce audit without mutation authority. It may select a mutating workflow only when the user's existing task already requests that outcome and scope. Selection never authorizes destructive, paid, irreversible, external, deployment, publication, production, or scope-expanding work.

References

Start with the ADR catalog. Select entries by Scope, Category, Tags, and Applies when:

• Read Short first.
• Read Long when a selected decision governs the task, a conflict exists, or implementation depends on its invariants.
• Read Guide only for current procedures, examples, commands, or compatibility notes.
• Do not load the entire library for a narrow task.
• Treat Long as canonical. Short cannot relax it; Guide is non-normative.

Route skill behavior through:

• Workflows: AC-ADR-064 Short · Guide.
• Validation: AC-ADR-049 Guide.
• Host state: AC-ADR-036 Guide.
• Execution and claims: AC-ADR-003 Guide · AC-ADR-004 Guide.
• Presentation: AC-ADR-050 Short · Guide.
• Adopted Jev host advice: AC-ADR-065 Short · Long · Guide; load for local adoption, host prerequisite evidence, or compliance audit.
• Conflicts: AC-ADR-046 Guide.

For provider mechanics, resolve the applicable public AC-ADR and load its Long first. Then conditionally read the internal ADR index and only AC-INTERNAL-001 for persistence resolution or AC-INTERNAL-002 for receipt rendering. Internal ADRs are implementation policy, do not enter target-repository adoption, and cannot relax an accepted public Long decision.

Use the catalog for namespace authority, lineage, canonical Long variants, and task-specific decisions. AC-ADR-001 is superseded historical context only.

For testing work, use the catalog to select AC-ADR-059 for repository validation ownership, AC-ADR-060 for runtime/state effects, AC-ADR-061 for distributed proof, and AC-ADR-062 for transform-cache evaluation. Select only applicable candidates; keep the seven-decision evidence-empty foundation unchanged. Map existing equivalent local decisions instead of duplicating them. Audit adopted outcomes without writes and distinguish met, unmet, unmeasured, waived, and not-applicable from execution statuses. Use the testing receipt within the target's existing evidence convention. Before promoting testing changes, derive public ADR, triplet and adoptable counts from the current catalog; reconcile the complete adoption matrix, decision locks/lineage and eval inventory, then verify regenerated/clean-installed skill byte identity and exclusion of fixture/eval files from installed payloads. Apply the AC-ADR-049 high risk floor when promotion changes a public governance or distribution contract, including changes expressed in documentation.

Inputs to inspect

After the route is resolved, inspect only what it needs:

• Outcome, repository identity/HEAD, protected Git/external state, and exact authorized scope.
• Repository instructions, ADR/index/mapping/history conventions, architecture/stack contracts, and validation receipts.
• Only representative code, tests, CI, public contracts, and migration/security/delivery evidence needed for the selected route.
• Supported instruction surfaces: nearest AGENTS.md, CLAUDE.md, existing CLAUDE.local.md, .claude/rules, .cursor/rules, and legacy .cursorrules only as migration evidence.

Do not classify CONTEXT.md as a Claude instruction file automatically.

Before persisting a spec, ADR, report, or instruction-surface change, route through AC-ADR-052 Short · Long · Guide. Start with Short and load Long before conditionally loading AC-INTERNAL-001 from the internal index for persistence-resolution mechanics. This dispatcher does not select or authorize a write surface.

Authority and collaboration

Use two independent axes:

1. Host/repository instructions, permissions, protected paths, user authorization, and safety constraints decide what may execute.
2. Applicable accepted or superseding ADRs decide intended architecture.

Current code proves current state, not intended policy. A requested accepted-ADR violation requires a visible warning naming the decision, conflict, affected scope, and resolution options; stop the affected implementation until a successor/adaptation is accepted or the conflict is withdrawn.

Rank architecture sources through AC-ADR-046: applicable accepted or superseding target ADRs; specific canonical target documentation; ADR-linked approved target examples; consistent current implementation; applicable adoptable provider decisions; then general framework defaults. Never blend contradictory sources into an undocumented compromise. Record the sources, affected scope and impact, recommended resolution, and decision owner, and stop only the dependent work. This ranking cannot expand the operational authority granted by the user, host, repository, or permissions.

If evidence changes the route materially, announce the reclassification and resolve its authority before continuing. Planning capability and filesystem permission are independent. Never claim prompt text changed either control.

Workflow

Load the AC-ADR-064 Guide and the matching report asset after selection and before producing an artifact or executing a mutation. Keep these entry gates visible:

setup

• Use target evidence for recommended or evaluate every accepted adoptable target-repository decision for complete. Only a new or evidence-empty repository receives AC-ADR-005, 006, 018, 019, 021, 022, and 049 as its initial candidate foundation. Setup never authorizes application refactoring, deployment, publication, or production probes.
• When AC-ADR-065 is selected, record the repository-native adoption mapping, authorized hosts, and prerequisite gaps through its Guide. Adoption does not activate hooks or authorize TypeSafe processing.

audit

• Preserve enforceable no-write behavior and perform a strictly read-only architecture, ADR-coverage, drift, and validation assessment. Create no artifact or mutation. For adopted Jev policies, report installed, configured, active/trusted, processing-authorized, current-inventory, and qualified evidence separately. Make no provider request or qualification/repair attempt; name unmet obligations while preserving native work.

refactor

• Verify accepted local ADRs govern and the request authorizes the whole bounded change. Stop on missing governance, conflict, unresolved durable choice, scope expansion, or material drift. Direct refactor never invents a durable decision or silently repairs governance.

plan-refactor

• Resolve and approve the bounded specification through native or conversational planning; after any required exit, persist only authorized governance artifacts and stop before source implementation.

plan-run-refactor

• Follow plan-refactor, then recheck state and execute only the unchanged approved plan in reversible slices. Stop on material drift, new decisions, failed proof, or scope expansion.

Plan lifecycle

Use the AC-ADR-064 and AC-ADR-036 Guides for detailed transitions and portable status handling:

1. Select the execution host lane from observed capabilities, independently of the target runtime. Report Planning capability as Active | Available but inactive | Unavailable | Explicitly declined | Indeterminate | Not applicable when material. Respect active or explicitly requested native Plan and recommend it for substantial ambiguous work. Inactive, missing, declined, or unknown controls do not alone block permitted read-only discovery and conversation; do not invent controls or claim a mode change.
2. Reuse prior answers and authority. Prepare the complete reviewable draft and exact delivery/write scope before one approval. A native final approval can cover content and writes only when its actual semantics do so; a mode toggle alone cannot. Preserve approval across required host transitions and ask again only for the affected material change.
3. Write no target repository/workspace artifact while Plan mode is active. Unknown mode or permission state never authorizes writes. Keep no-write conversation and proven non-mutating reads available while resolving a necessary transition. An explicit native-Plan request remains pending until observed active; honoring a declined recommendation does not silently exit active Plan.
4. Recheck state after approval and Plan-mode exit when required, before persistence or execution. plan-refactor saves only authorized approved governance or completes explicit chat-only delivery without claiming persistence; source implementation belongs to separately authorized execution. Proposed ADR persistence does not accept its decision.
5. Use structured or asynchronous questions only when supported. Continue only independent authorized work while a required answer is pending. Silence, timeout, and preselected options are not approval.

Conditional stable-skill selector instruction

Classify this target-repository instruction as applicable, not applicable, or indeterminate. It is applicable only when evidence proves the target publishes a stable public skill with multiple material workflows.

• In setup, preserve an equivalent rule or add a generic rule requiring complete finite workflow disclosure, intent-bound selection and rationale, an ambiguity question, mutation only within already-authorized outcome/scope, and separate high-risk/external approvals.
• In audit, report the classification and any missing/equivalent/conflicting rule without writing.
• Direct refactor does not repair a missing rule; route governance repair to setup.
• indeterminate never authorizes a write.
• Never copy this repository's or the provider skill's ADR ID into the target. Use repository-native identity only when local governance requires a decision.

Public statuses

When material, use the exact evidence-backed Read-only enforcement, Architecture decision status, and Execution status values in the AC-ADR-036 Guide and report asset. Planning and filesystem enforcement remain independent. completed covers only the authorized slice/stages; it implies no CI, publication, deployment, production, or third-party success.

For concise user-facing outcome lists, route status semantics through AC-ADR-050 Short and presentation through AC-ADR-053 plus the conditional internal renderer route above.

Assets

Assets are derived and non-normative. Use assets/setup-report-template.md for setup and assets/refactor-report-template.md for the other routes; use the remaining assets only for authorized governance work. Applicable canonical Long ADRs prevail.

Scripts

Architecture Compass ships no executable runtime scripts. Use repository-native validators only after their behavior and write effects are understood; do not invent or install a helper as part of audit.

Safety rules

• Do not invent repository facts, paths, commands, ADRs, mappings, validation, or host capability; do not infer mutation from ambiguity.
• Never override accepted target ADRs with bundled decisions or turn audit into setup, planning, or implementation.
• Do not install, invoke, vendor, or configure a public skill merely because it is available or recommended.
• Do not expose secrets, customer data, private provenance, or internal hostnames in reusable artifacts.
• Destructive, irreversible, external, deployment, publication, production, and scope-expanding work requires separate authority, exact target, stop conditions, and recovery evidence.
• Do not duplicate proof obligations, reuse invalidated receipts, create ceremonial permanent smoke harnesses, or overstate evidence stage.
• Stop on scope drift, missing authority, protected-path overlap, ambiguous mapping, unresolved ADR conflict, or failed required validation.

Output format

Use the matching report asset and AC-ADR-004 evidence table. Include the workflow set and selection, coverage, write scope/status/protected state, inspected and unavailable evidence, decisions/mappings or findings, approved plan or changes, AC-ADR-049 ledger, risks/deferred triggers, and next authorized action.

Render the final receipt through AC-ADR-053 and its conditional internal adapter route; keep this section limited to output assembly rather than duplicating their durable presentation policy.

For audit, provide findings in severity order without patches or repository writes. For plan routes, distinguish approved content and write scope, pending transitions/persistence, persisted artifacts, state-recheck result, and executed work.

Completion criteria

Apply the selected procedure's criteria in the AC-ADR-064 Guide and reconcile its AC-ADR-049 receipt. Completion covers only the authorized workflow and evidence stages.

Failure modes

Apply the route and Plan stops in the AC-ADR-064 Guide and validation recovery in the AC-ADR-049 Guide. Never turn a blocked or indeterminate state into a completion claim.