Local context wedge

Give local agents a boundary before they touch tools, data, or money.

Micro ECF is the local context wedge for builders. It creates repo artifacts that tell a local agent what it may read, cite, call, remember, export, and send into a Triptych OS preview.

Product rule: Micro ECF prepares the local boundary. ECF Core is the open-source self-hosted context layer. Triptych OS is the deployment product. Full ECF stays private/internal. Micro ECF is not a semantic RAG engine, vector store, hosted answer pipeline, wallet, settlement rail, or Full ECF runtime.

Install Micro ECF Read the Guide Preview in Triptych OS
Micro ECF repo ECF Core repo Harness overview Policy schema

Context

Bound what the agent can know

Declare allowed context, denied sources, memory scope, tenant or project boundaries, and what should be summarized instead of copied into the agent's working context.

Tools

Separate allowed calls from blocked actions

Describe which tools, APIs, domains, repos, and handoff routes the local agent can use before it becomes a hosted deployment with real runtime permissions.

Money

Set spend and approval rules early

Put daily spend caps, per-action thresholds, approval requirements, and first-proof limits in the packet before the agent can consume treasury funds or sell through paid routes.

Swarms

Control handoffs between agents

Define how many agents can participate, what each role can do, when work must stop for owner review, and what evidence must be produced before the swarm expands.

Why use Micro ECF before Triptych OS?

It gives builders a no-spend way to make local agent behavior inspectable before asking the hosted platform to create runtime, treasury, public API, marketplace, or x402 exposure.

Less rewrite

Keep your agent, model, repo, and framework local. Micro ECF wraps the operating boundary instead of forcing a platform migration first.

Less ambiguity

The Harness packet says what the agent is allowed to access, spend, remember, approve, and expose before the first live run.

Cleaner handoff

Triptych OS receives a structured deployment request instead of a vague prompt, screenshot, or informal demo description.

Roadmap for Syrin users

The roadmap graphics are intentionally text-free so they can be reused in Discord, guides, and product decks. The labels below explain what each image means without turning the PNGs into inaccessible screenshots.

Open Syrin Guide View Roadmap Images
Five-stage Micro ECF to Triptych OS roadmap: local context, Harness export, Triptych OS handoff, governed autonomy, and earned autonomy.
The full path is: Local Context to Harness Export to Triptych OS Handoff to Governed Autonomy to Earned Autonomy. Micro ECF covers stages 1-2. Triptych OS owns live runtime, wallet budgets, receipts, marketplace access, and autonomy gates.
Stage 1 detail showing local repo, docs, database, API docs, policy gate, output artifacts, and blocked secret-like sources.

1. Local context

Install Micro ECF, inspect the read-only plan, and create local policy/context artifacts only after approval. This stage blocks secret-like sources before an agent gets a packet.

Stage 2 detail showing local artifacts flowing into an Agent OS Harness preview card with no-spend status.

2. Harness export

Build source-map, policy-summary, context-packet, and harness-export files. This is still local and no-spend.

Stage 3 detail showing Harness handoff through an approval gate into hosted runtime, wallet, API, and monitoring panels.

3. Triptych OS handoff

Run deploy readiness and deploy preview before recording a deployment request. Hosted runtime starts only after owner approval, budget policy, and trust checks.

Stage 4 detail showing pre-action review, parallel work branches, merge, post-action reconciliation, and feedback loop.

4. Governed autonomy

Triptych OS adds review, budget, receipt, and reconciliation gates before useful live work. Micro ECF remains the context input, not the executor.

Stage 5 detail showing an earned autonomy control hub with marketplace, multi-agent, trust, and learning panels.

5. Earned autonomy

Expand only after repeated proof, trust evidence, and explicit owner approval. This is the end state, not the default after installing Micro ECF.

Positioning

Agoragentic is Triptych OS for deployed agents and swarms. Router / Marketplace is the transaction network. ECF is the context/governance engine.

Package boundary

The open-source package boundary is agoragentic-micro-ecf with the micro-ecf CLI: init, scan, doctor, lint, index, build-packet, export --agent-os, and serve-mcp. The agoragentic-harness contract bridges those local packets into hosted Triptych OS preview.

Validate local policies with micro-ecf-policy.v1.json and exported packets with agent-os-harness.v1.json.

ECF Core vs Full ECF

Micro ECF is the installable local wedge. ECF Core is the separate open-source self-hosted context-governance runtime for builders who need more than static artifacts. Full ECF remains private/internal infrastructure, not a public enterprise package.

One local command flow

Start locally, inspect what gets included or blocked, then export a no-spend Triptych OS Harness packet when the boundary is ready. 

npx agoragentic-micro-ecf@latest explain
npx agoragentic-micro-ecf@latest plan --dir .
npx agoragentic-micro-ecf@latest install --dir . --yes
npx agoragentic-micro-ecf@latest doctor --dir .
npx agoragentic-micro-ecf@latest scan --dir .
npx agoragentic-micro-ecf@latest lint ECF.md
npx agoragentic-micro-ecf@latest index ./docs --output-dir .micro-ecf
npx agoragentic-micro-ecf@latest build-packet --policy .micro-ecf/policy.json --source-map .micro-ecf/source-map.json --output-dir .micro-ecf
npx agoragentic-micro-ecf@latest export --agent-os --policy .micro-ecf/policy.json --output .micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_api_key npx agoragentic-os@latest deploy readiness --file .micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_api_key npx agoragentic-os@latest deploy preview --file .micro-ecf/harness-export.json
AGORAGENTIC_API_KEY=amk_your_api_key npx agoragentic-os@latest deploy create --file .micro-ecf/harness-export.json

readiness and preview are no-spend checks. deploy create records the hosted Triptych OS deployment request; funding, provisioning, public API exposure, marketplace selling, and x402 monetization remain separate approval-gated steps.

Paste the repo into your IDE LLM

A developer should be able to paste the Micro ECF GitHub folder into Cursor, Codex, Claude, Gemini, VS Code, or a database-assistant workflow and have the LLM explain the tool, show the local install plan, then wait for approval before writing files. 

https://github.com/rhein1/agoragentic-integrations/tree/main/micro-ecf

1. Explain first

The LLM should explain that Micro ECF builds local source maps, blocks secret-like paths, builds citation-ready governance packets, and prepares Triptych OS preview files. It should not describe Micro ECF as a semantic RAG engine.

2. Plan without writes

It should run npx agoragentic-micro-ecf@latest plan --dir . first. The plan is read-only and lists every file that may be created.

3. Install only after approval

Only after the developer approves should it run npx agoragentic-micro-ecf@latest install --dir . --yes. Without --yes, install refuses to write.

New chats are explicit

Micro ECF persists as repo artifacts, not hidden global chat memory. Compatible IDE agents can auto-read AGENTS.md plus the generated ECF.md; other chats should receive MICRO_ECF_LLM_BOOTSTRAP.md at the start of the conversation.

Ask for disclosure

A useful assistant should say whether it read .micro-ecf artifacts, used a configured Micro ECF MCP server, used direct repo reads only, or did not use Micro ECF.

Persistent tool option

IDEs that support local MCP servers can run npx agoragentic-micro-ecf@latest serve-mcp --root .micro-ecf so future chats can query the local context layer instead of relying only on pasted instructions. After install, the local CLI form is micro-ecf serve-mcp --root .micro-ecf.

Open

What builders can adopt locally

Context packet schema, budget policy schema, tool policy schema, approval policy schema, memory policy schema, swarm policy primitives, local policy simulation, harness export helpers, example adapters, example receipts, and ECF Core self-hosted context-governance contracts.

Closed

What stays inside the hosted platform

Hosted router ranking, trust and reputation scoring, wallet and payout orchestration, settlement internals, private connectors, deployment control plane internals, operator workflows, and the private/internal Full ECF runtime.

Output

The artifact is a deployment-ready Harness packet

Micro ECF should produce a durable ECF.md plus a packet with agent manifest, context policy, tool policy, budget policy, approval policy, memory policy, swarm policy, deployment policy, and agent_os_preview_request.

That packet can fill the Triptych OS launch planner, create a no-spend preview, and preserve the local policy boundary without exposing private local internals.

Adopt when

Use it when the agent is becoming operational

Use Micro ECF when a local agent is about to touch private context, call external tools, spend money, coordinate multiple agents, or move from local proof to hosted Triptych OS.

Skip it for one-off throwaway prompts where no context, tool, memory, spend, or deployment policy needs to survive the session.

1. Define policy

Describe context, tools, budgets, approvals, memory, deployment exposure, and swarm limits.

2. Export Harness

Export a Triptych OS Harness packet that matches agoragentic.agent-os.harness.v1.

3. Deploy when ready

Preview the packet in Triptych OS, record a deployment request, fund treasury, run first proof, then gate marketplace or x402 exposure.