Governed agent stack
One agent stack. Four explicit controls.
Reach, action, context, and evidence compose without pretending that installation alone governs every call.
Execution model
The host chooses the route. Each layer proves one job.
ProductLoop coordinates the workflow. Qarinah compiles approved project context. Maqam decides whether a registered operation may execute. Cockroach Crawler collects bounded public evidence. Results return as records, receipts, and context references.
- 01
Compose
ProductLoop OSWorkflow runtime, policies, approvals, connectors, skills, evaluations, provenance, and research plans.
- 02
Contextualize
QarinahLocal event ledger, deterministic graph/index, and compact cited context packs. Public npm 0.1.5+ with a 0.1.6-compatible handoff contract.
- 03
Govern
MaqamRegistered tool policy, exact one-use approvals, browser-action contracts, traces, and evidence.
- 04
Reach
Cockroach CrawlerBounded public-web reads, provider capability checks, normalized source records, and serverless fetch policy.
Capability truth
What the combined system can claim today.
Every row names the component that provides the behavior and the boundary the deployment must still enforce.
| Capability | Component | Status | Deployment boundary |
|---|---|---|---|
| Public URL crawl to Markdown or JSONL | Cockroach Crawler | Available | Explicit origin and resource policy; public network by default. |
| Public GitHub read/search without a developer key | Cockroach Crawler | Available | Unauthenticated REST limits; read-only operations. |
| Known-video metadata without a developer key | Cockroach Crawler | Partial | Public metadata and a restricted pinned no-key route; official search uses an API key. |
| RSS/Atom and available YouTube captions | Maqam source adapters | Configured | The host supplies and governs the selected reader or executable. |
| Natural-language browser actions | Maqam browser contract plus a host driver | Adapter-side | No browser engine or model provider is silently bundled. |
| Exact approval and replay rejection | Maqam | Available | The real side effect must pass through the registered gateway. |
| Durable compact project context | Qarinah | Public 0.1.5+ | The handoff contract is 0.1.6-compatible; explicit workspace consent and machine-local trust remain required. |
| Cross-package workflow and evaluation | ProductLoop OS | Available | External browsers, models, secrets, identity, and durable services remain deployment choices. |
Original composition
Learn from strong tools without cloning their product.
Broad capability installers demonstrate the value of one command and a useful doctor. In-page agents demonstrate low-friction browser control. Knowledge graphs demonstrate compact retrieval across project relationships. This stack keeps a different center: governed execution and evidence-linked context across replaceable adapters.
- No imported upstream branding or silent dependency
- No claim that free access is unlimited or provider-approved
- No browser-cookie extraction or login reuse
- No claim that an in-process policy is an operating-system sandbox
Try the public layers
Check web reach, then prove exact approval.
Cockroach Crawler reports source access, Maqam demonstrates its separate tool-approval boundary, ProductLoop composes workflows, and Qarinah 0.1.5+ provides compact cited handoffs.
npx -y --package cockroach-crawler@0.7.0 cockroach-sources doctor
npx -y --package cockroach-crawler@0.7.0 cockroach-reach doctor
npx -y maqam@0.3.3 demo approval
npx -y qarinah@0.1.6 --helpBoundaries
What one install cannot promise.
Does the stack include a model or paid API?
No. Model providers are deployment choices. Public web, GitHub, and selected optional routes may work without a developer key; every provider keeps its own authentication, login, terms, and availability constraints.
Does Maqam automatically control every browser or shell?
No. Only registered operations routed through the gateway are governed. Direct shell, browser, SDK, or provider calls bypass that boundary.
Is Qarinah publicly installable?
Yes. Qarinah is public on npm at 0.1.5+; the documented handoff contract is compatible with the coordinated 0.1.6 release. Workspace consent and machine-local trust are still required.