Specification
Machine-readable Core and Extensions for HALOS alignment
HALOS Specification v1.0.0
Machine-readable source: manifest.json, core.json
Core (Required)
Projects implementing HALOS must adopt all core requirements.
HALOS-CORE-1 — Human Primacy
Humans are originators of meaningful creative direction. Agents assist and amplify; human judgment overrides agent output when in tension.
Source: /principles.html#1-human-primacy
HALOS-CORE-2 — Ideas as Assets
Ideas and creative works have intrinsic value. Originators can claim authorship; lineage can be traced; value flows to contributors.
Source: /principles.html#2-ideas-as-assets
HALOS-CORE-3 — Attribution and Provenance
Contribution must be traceable. Human contributions identifiable; agent involvement disclosed; provenance representable.
Source: /principles.html#3-attribution-and-provenance
HALOS-CORE-4 — Transparency of AI Involvement
When AI participates in creation, that participation must be visible. No hidden or undisclosed agent contribution when it matters.
Source: /principles.html#4-transparency-of-ai-involvement
HALOS-CORE-5 — Ethical Guardrails
Human–agent collaboration operates within ethical boundaries. Harmful uses out of scope; no deception about AI involvement; human agency preserved.
Source: /principles.html#5-ethical-guardrails
HALOS-CORE-6 — Evolving Standards, Stable Principles
Standards and specifications may change; principles should not. Principles are the anchor.
Source: /principles.html#6-evolving-standards-stable-principles
HALOS-CORE-7 — Governance Through Proposal
The framework evolves through open proposal and review. Changes follow a documented process.
Source: /principles.html#7-governance-through-proposal
HALOS-CORE-8 — Innovation with Accountability
Experimentation is encouraged; innovators must articulate how their work aligns with or departs from the principles.
Source: /principles.html#8-innovation-with-accountability
For ecosystem context and future mappings, see Related Specs.
Get Involved
The HALOS specification is developed openly. The halos-spec repository is the canonical source for schemas, the adoption toolkit, and the principles document.
For adopters — use the adoption guide and templates to implement HALOS in your repository. Or copy the agent prompt and let your AI coding agent self-adopt.
For contributors — propose spec changes through the governance process, then open a pull request in halos-spec. The JSON schema is the validation source of truth.
For implementors — machine-readable spec files: manifest.json, core.json. Star or watch halos-spec to track changes.