One workspace for docs, agents, governance, and delivery.
React/Vite app with Apollo clients for ingestion, feed, synthesis, CMS, and context.
Federation gateway composing ingestion, synthesis, feed, and CMS subgraphs.
Cloudflare Worker GraphQL subgraph for RSS sources, raw articles, and clusters.
AI synthesis and Ask AI over clusters, using ingestion, oc-cognee, and Workers AI.
GraphQL wrapper around oc-cognee temporal facts and knowledge graph routes.
Railway Python service for temporal facts, hybrid retrieval, and graph queries.
Solo builders and engineering teams keep reaching for the same four primitives. Arca ships them as one harness so the agents, the people, and the work stay in sync.
One vault holds the project, the agents, and the documents. Sessions end; state stays. No work lost between runs.
Constitutions per manager, provider fences, claim tokens, and an append-only ledger. Agents act inside lines you set.
Spawn, name, and retire managers and workers from one canvas. Each one keeps its role, its prompt, and its history.
Every frame, claim, and outcome is written to a timeline you can replay. See what an agent did, why, and when.
Arca is shaped by the two groups already shipping with agents today. The needs overlap; the surface is the same.
Run a personal program desk: spawn agents for product, code, review, and release; keep the documents, the chat history, and the project state in one vault you own.
For startup, midsize, and enterprise teams running a hybrid model: agents take the well-shaped work, engineers take the judgement calls, and the harness keeps the handoff legible.
Sessions end; state stays. Arca writes every agent, prompt, and document into a local-first vault you own, so a builder picks up tomorrow exactly where the agents left off tonight.
name: program-manager role: CEO of the workspace defaultModel: claude-sonnet-4-20250514 directives: - Delegate technical deep-dives to TPM - Keep one active PgM handoff at a time - Log every delegation to the activity ledger - Block cross-workspace file reads fences: providers: [claude, openai] maxTokens: 200000 crossWorkspace: deny
name: technical-pm role: delivery architect directives: - Own migration plans and build scopes - Route judgment calls to Staff Engineer - Spawn workers only after scope is legible handoffs: active: staff-engineer reason: encryption rollout review
name: code-qa role: verifier directives: - Check tests before review - Flag missing evidence - Write findings back to the timeline
# Sprint planning 1. Gather candidate issues 2. Confirm ownership with TPM 3. Assign shaped work to agents 4. Keep human review on release-risk items
# Release checklist - migrations reviewed - docs updated - provider fences checked - audit ledger exported - staging deploy verified
# API contract status: draft owner: Technical PM Endpoints touched by the encryption rollout must keep the legacy event shape for two releases.
{"time":"14:32","type":"delegate","from":"PgM","to":"TPM","task":"encryption-rollout"}
{"time":"14:28","type":"review","actor":"Arjun Mehta","task":"release-blockers"}
{"time":"14:25","type":"exit","worker":"arca-9","result":"adapter-docs"} workspace: acme-platform methodology: scrum activeSprint: sprint-7 defaultReviewOwner: Arjun Mehta
# Q3 release train status: active owner: Program Manager Children: - encryption-rollout.md - review-sla.md - adapter-docs.md
# Encryption rollout migration owner: Arjun Mehta status: in-review Next: - verify rotation handler - confirm parallel-run window - write release note
# Review SLA owner: Staff Engineer status: queued Keep human review under four hours for release-blocking work.
# Sprint 7 goal: Q3 release channel points: 31 stories: 6 Focus: - encryption rollout - adapter pluggability docs - cross-workspace fence
{
"providers": ["openai", "claude"],
"maxWorkers": 4,
"crossWorkspace": "deny",
"audit": "append-only"
} providers: claude: allowed openai: allowed ollama: local-only gemini: blocked fallback: require-human-approval
{"time":"14:31:44","type":"deny","summary":"Cross-workspace read denied"}
{"time":"14:32:06","type":"fence","summary":"Provider fence checked"}
{"time":"14:32:08","type":"spawn","summary":"Worker arca-7 spawned"} name: Arjun Mehta title: Staff Engineer responsibilities: - own judgment calls - review encryption rollout migration - unblock release-risk work
Every agent has a named manager constitution that holds its role, prompt, and history. Solo builders run the full set themselves; teams assign disciplines per agent. Replies land in the same ledger, never a side channel.
Engineers take the judgement calls; agents take the well-shaped work. Drag a card to Review and the agents replan. The handoff stays legible and the queue stays one queue.
Constitutions, provider fences, claim tokens, cross-workspace fences, and an append-only ledger. Solo builders set the policy themselves; teams roll it out once and audit centrally.
Arcatect can propose rebuilds; operator approves before restart.
Running, blocked, and finished workers stay visible to the operator.
Future [SPAWN] directives surface as approval cards before launch.
Frames, claims, and outcomes land on a tape you can scroll, filter, and replay. Debug a run; audit a release; show the board what the agents shipped this week.
“I run six agents on my own product. The vault means I never have to re-explain the project on Monday morning.”
“Our hybrid team finally has one queue. Engineers and agents work the same board, and audit is a tab away.”
“Constitutions per agent and an append-only ledger were the unlock for security review. We rolled it out org-wide in a week.”
“I am the operator and the engineer. Arca holds the documents, agents, and history so I can keep shipping at one-person scale.”
“I run six agents on my own product. The vault means I never have to re-explain the project on Monday morning.”
“Our hybrid team finally has one queue. Engineers and agents work the same board, and audit is a tab away.”
“Constitutions per agent and an append-only ledger were the unlock for security review. We rolled it out org-wide in a week.”
“I am the operator and the engineer. Arca holds the documents, agents, and history so I can keep shipping at one-person scale.”
Arca is free to download and use while the harness is in private beta. Solo plans stay generous; team and enterprise plans land when beta closes. Existing workspaces keep their data.
For one operator running their own fleet. Bring your own provider keys.
For startup, midsize, and enterprise teams running hybrid workflows.
Contact usPersistence, governance, agent management, and observability — built for the way humans and agents actually ship together.