Reference Operations Policy

Policy and governance

The authoritative workflow is standard-pr-practice, reached through AGENTS.md and CLAUDE.md. Its complete standards index contains the preserved rules and conflict precedence. The removed Kiro generator is not part of the current workflow.

Repository gates

• Path policy checks PascalCase file stems, ASCII spelling, and directory density.
• Python checks cover formatting, lint, typing, explicit imports, and steering.
• SPDX, workflow pinning, workflow security, and preserved-standards checks protect repository metadata.
• CI Agg inventories applicable CI; reviewer status is separate.
• Merge queue acceptance defers heavy work on PRs and runs acceptance and heavy security analysis on merge-group candidates.

The checked-in queue guide describes intended operation. Live GitHub rulesets must be inspected before enrollment; this documentation does not prove that those settings are active or that every required gate is enforced. Never infer queue acceptance from green PR checks or alter protections to obtain a merge.

Documentation and gotchas

Every repository addition requires a new change entry, relevant guide updates, and links in the PR. Discoveries must be recorded in Gotchas before finishing. Generated documentation receives the same review, source verification, naming, and licensing checks as manually authored content.

Security and acceptance

Follow SECURITY.md for reporting and archive validation for concrete input limits. Security scanners and structural policy checks establish different facts; neither proves that a target CAD application can load, edit, and rebuild a converted model.

Research exemptions are scoped to re/. Production output still requires no CAD runtime, no donor blocks, and lossless parametric acceptance.