Intake and boundary checks
Classify an incoming task and its data boundary before a tool or record is allowed into the workflow.
← eijex home
AgentOS · Public code
Human-supervised workflow integrity.
AgentOS is the open control-plane foundation for policy checks, approval gates, audit trails, and evidence-safe public projection across Eijex research workflows.
Control planeHuman approval requiredSynthetic fixtures
Responsibility boundary
Control, not scientific truth.
AgentOS governs how work moves between tools and people. It does not replace FactorForge's computation, own ValidationHub's evidence records, or decide that a biological claim is true.
AgentOS control plane
Policy · approval · audit · public projection
FactorForge
Design computation
Produces reproducible CDS candidates and computational review artifacts within its own scientific boundary.
ValidationHub
Evidence registry
Preserves identity, lineage, review state, and evidence-package references without turning workflow approval into evidence.
Control surfaces
Explicit decisions at every public boundary.
Claim review and approval
Keep external statements behind an explicit human decision instead of allowing an automated run to publish them directly.
Audit and replay
Retain structured decisions, policy results, and artifact references so a workflow can be reviewed without treating the log as scientific evidence itself.
Approval contract
Automation can prepare. A person authorizes release.
Public projection remains a distinct action with an attributable decision. A successful tool execution alone is not permission to publish a claim or a permissioned record.
{
"artifact_hash": "sha256:…",
"boundary_check": "pass",
"approval_state": "required",
"public_projection": false
}Current public boundary
What is available today
Public
Workflow code, schemas, policy checks, tests, documentation, and synthetic fixtures in the canonical GitHub repository.
Not implied
No separate hosted AgentOS application, autonomous scientific authority, or public store of permissioned research evidence.
Code, public schemas, documentation, and synthetic fixtures are open. Raw sequences, partner documents, personal information, and permissioned experimental evidence are governed separately and are not published in the software repositories.
Inspect the public control plane.
Start with the source, schemas, tests, and synthetic examples.