Branch main Arch compliance rules

Compliance Rules

Back to Branch Overview

Field	Value
Branch	main
Source	specs/architecture/compliance_rules.md
Commit	774b981ef226
Synced (UTC)	2026-07-14T05:14:42Z

Visual Context

Architecture pages define ownership, authority, and dependency direction for the base design.

flowchart TB
  ASH["ASH fixed authority"] --> Aeostara["Aeostara base design"]
  Aeostara --> Contracts["Contracts and algorithms"]
  Aeostara --> Handoff["Downstream handoff"]
  Handoff --> Platforms["Windows / Mac / iOS repos"]

Loading

Reading Checklist

Question	Where to look
Who owns the semantic decision?	Check the authority and boundary language.
What is platform-neutral?	Find Aeostara-owned obligations.
What moves downstream?	Find adapter, implementation, and deviation rules.

---

Source Content

Compliance Rules

Meaning of Compliance

In this repository, compliance means downstream conformance to ASH semantic authority plus Aeostara execution-safety mechanics.

Semantic Compliance Rules

1. ASH is upstream semantic authority.
2. Aeostara must consume ASH-derived diagnostics, classification, and recoverability semantics.
3. Surface-difference evidence and actuator projections must derive from the ASH-aligned decision flow.
4. Fallback, containment, and safe-halt decisions must be explicitly represented.
5. Diagnostic artifacts must use schema/taxonomy-compatible fields.

Execution-Safety Rules

1. Policy gates must run before mutation.
2. Backup is required before mutation execution.
3. Post-execution verification is required.
4. Rollback/escalation paths must be deterministic and auditable.
5. Audit eventing is mandatory for decision-critical actions.

Repository Automation Rules

CI must validate:

• Presence of required conformance artifacts
• Schema validity of contract layer
• Presence of current ASH-built downstream artifacts
• Acceptance and traceability artifacts present and coherent