Polaris: Skill for Claude Code

Architecture Invariant Verification

Objective

Keep accepted Polaris architecture continuously executable and regression-protected.

This skill owns one repository invariant gate:

The complete architecture suite passes with zero failures, and the live greenfield repository has zero mechanically detectable architecture violations.

The architecture guard and its tests are executable representations of accepted architecture. They are not architecture authority themselves. Resolve architectural meaning from the current non-legacy authority ordering in AGENTS.md.

Applicability

Invoke this skill when the candidate can affect a mechanically enforced architecture invariant, including when it changes:

• current Python source under src/polaris/;
• current tests under tests/;
• current Python migrations scanned by tests/architecture_guard.py;
• tests/architecture_guard.py or any architecture-guard test;
• accepted architecture authority whose mechanically enforceable rule is represented by the architecture guard.

Do not invoke it merely because unrelated documentation, tracker state, Project projection, or other non-architecture administrative state changed.

Applicability controls whether the gate runs. Once applicable, verification scope is the complete architecture suite; do not narrow it to changed files, one ticket, one Spec obligation, or one rule.

Architecture Rule Admission Invariant

A rule belongs in the architecture guard only when all of the following are true:

1. current accepted authority establishes a durable architectural invariant;
2. the invariant is mechanically observable from the repository surface the guard can inspect;
3. detection can be implemented with sufficiently low false-positive risk;
4. the checker and independent falsifier tests can express both prohibited and adjacent-valid states where material.

Do not turn style preferences, speculative future architecture, subjective design taste, or ordinary code-quality concerns into architecture rules.