Harness Runtime and DataHub Projection
Harness Runtime and DataHub Projection
Section titled “Harness Runtime and DataHub Projection”FractalOps keeps one execution kernel. Studio, Ouroboros, and AgentSquad are product flows on top of Harness Runtime, not competing schedulers.
Boundary
Section titled “Boundary”- Harness Runtime owns run-attempt graph state and reconciliation projection.
- Temporal owns durable retry, timers, and workspace lease lifecycle.
- FractalOps Harness task cells are implemented inside Harness Runtime. They are an internal control-plane contract, not a separate product plane or runtime name.
- DataHub owns catalog, lineage, ownership, impact navigation, and drift discovery.
- DataHub does not own identity, mutation authority, secret authority, or proof closure.
- Proof closure requires Semantics identity, ClickHouse fact, and Chronicle evidence.
Projection Contract
Section titled “Projection Contract”FractalOps emits compact DataHub operations for these aspects:
fopsProjectAspectfopsAgentSquadAspectfopsAgentGenerationAspectfopsAgentRoleAspectfopsArmoryLoadoutAspectfopsMcpRuntimeAttachmentAspectfopsTaskOrchestrationAspectfopsRunAttemptAspectfopsWorkspaceLeaseAspectfopsBrowserLeaseAspectfopsSearchGroundingAspectfopsMemoryArchiveAspectfopsProofClosureAspect
The projection stores refs and summaries. Raw heartbeats stay in ClickHouse, long evidence stays in Chronicle, and long memory/wiki content stays in Agent Memory Archive.
Isolation Rules
Section titled “Isolation Rules”- Project identity is
tenant_id + project_slug + squad_key. - Agent identity is
agent_role_lineage_key = squad_key::agent_id. - Generation, continuity, and attempt are separate concepts.
- Daytona workspace-per-agent is forbidden. One project workspace may host per-agent slots.
- PlaywrightGrid sessions are per-agent browser leases. Agent launches default to the
agent-runnertool profile: reset/open/auth/snapshot/action CLI helpers plus a narrow browser evidence surface. - SUIT actor credentials are per-role actor leases.
- Armory loadout is the canonical MCP, skill, policy, credential, and isolation contract.
Failure Prevention
Section titled “Failure Prevention”- Do not add scheduler state to Studio, Ouroboros, or AgentSquad.
- Do not let DataHub close proof alone.
- Do not let SearXNGgrid search output become truth without proposal and evidence closure.
- Do not expose agent-visible secrets; emit secret refs and credential modes only.
- Do not give
closergeneral code write authority. It owns DataHub/RDF/doc closure.