Keep deterministic logic deterministic
If a requirement can be expressed safely and completely in ordinary code, it does not need semantic evaluation.
About Antaeus
Policy infrastructure should make accountability easier to see.
Antaeus began from a practical question: how can an application use semantic judgment without reducing a consequential policy to an opaque prompt and an undocumented answer?
Project purpose
Move policy meaning into artifacts people can inspect.
Meaning-heavy requirements often begin as prose, prompts, or branches scattered through application code. Antaeus is building a narrow infrastructure boundary where those requirements can become versioned policy artifacts, named cases, explicit outcomes, and traceable evidence.
The goal is not to automate responsibility away. It is to make the policy, evaluator route, uncertainty, and application handoff visible enough for engineers and accountable people to reason about them.
Working principles
Narrow boundaries. Explicit evidence. Honest maturity.
These principles shape both the public project and how its current state is described.
Separate judgment from authority
Antaeus returns a policy decision. Authentication, authorization, transactions, side effects, and final system authority stay with the application.
Record failure as failure
Operational failure must not be silently relabeled as policy denial, human review, or permission to proceed.
Claim only what evidence supports
A synthetic fixture can verify contracts and plumbing. It cannot establish semantic quality or production readiness.
Project structure
An independently useful core comes first.
The public repository owns reusable policy infrastructure. Commercial or hosted work does not bypass its review, compatibility, or governance process.
Available as source
Public open-source project
Portable contracts, the Go core and CLI, evaluator extension points, conformance fixtures, examples, governance, and Apache-2.0 licensing.
See what works nowExperimental beta
Hosted operating workflow
Use the hosted dashboard and API to publish policies, evaluate content, and inspect decisions. The service has shared capacity and no production SLA.
Read the hosted API guideSeparate evidence track
Research program
Semantic Policy Enforcement research asks whether the boundary works under a frozen evaluation. The implementation is an instrument, not the finding.
Understand the evidence boundaryStewardship today
Maintainer-led, with the concentration stated plainly.
Antaeus is currently a maintainer-led project. Initial maintainers set scope, approve public contracts and releases, and remain accountable for security, compatibility, and repository stewardship.
Routine work happens through issues and pull requests. Material changes to architecture, security, compatibility, governance, or project scope require a written decision record. Broader maintainership is intended to follow sustained contribution and demonstrated judgment, not a premature claim of community governance.
Participation
Start with a concrete question or a reproducible change.
The repository is the source of truth for the current implementation, contribution expectations, issue history, and private vulnerability reporting. Early contributions are most useful when they stay narrow and make the contract easier to test or understand.
To reach the maintainers directly with questions, feedback, or partnership inquiries, email hello@antaeus.io.