{"id":51433513,"url":"https://github.com/rhein1/agoragentic-micro-ecf","last_synced_at":"2026-07-05T05:30:27.689Z","repository":{"id":365368713,"uuid":"1271794445","full_name":"rhein1/agoragentic-micro-ecf","owner":"rhein1","description":"Micro ECF: the open local context wedge. A dependency-free CLI + MCP server that compiles your repo into durable, policy-governed local artifacts (ECF.md, source maps, policy summaries, Agent OS Harness exports) a coding agent reads before it edits. No cloud, no wallet. The smallest ECF tier.","archived":false,"fork":false,"pushed_at":"2026-07-04T17:01:43.000Z","size":3126,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-07-04T18:06:45.386Z","etag":null,"topics":["ai-agents","claude-code","cli","codex","coding-agent","context-engineering","context-governance","cursor","ecf","llms-txt","local-first","mcp","micro-ecf"],"latest_commit_sha":null,"homepage":"https://agoragentic.com","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/rhein1.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-06-17T02:43:20.000Z","updated_at":"2026-07-04T16:14:43.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/rhein1/agoragentic-micro-ecf","commit_stats":null,"previous_names":["rhein1/agoragentic-micro-ecf"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/rhein1/agoragentic-micro-ecf","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rhein1%2Fagoragentic-micro-ecf","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rhein1%2Fagoragentic-micro-ecf/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rhein1%2Fagoragentic-micro-ecf/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rhein1%2Fagoragentic-micro-ecf/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/rhein1","download_url":"https://codeload.github.com/rhein1/agoragentic-micro-ecf/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rhein1%2Fagoragentic-micro-ecf/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":35144844,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-07-05T02:00:06.290Z","response_time":100,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai-agents","claude-code","cli","codex","coding-agent","context-engineering","context-governance","cursor","ecf","llms-txt","local-first","mcp","micro-ecf"],"created_at":"2026-07-05T05:30:27.159Z","updated_at":"2026-07-05T05:30:27.683Z","avatar_url":"https://github.com/rhein1.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Micro ECF\n\nMicro ECF is a lightweight local context layer for builders who want safer agents.\n\nIt builds local source maps, policy summaries, and citation-ready context packets from bounded repo/docs/database-summary inputs, then exports Agent OS Harness files for no-spend deployment preview.\n\n```bash\nnpx agoragentic-micro-ecf@latest init --dir .\nnpx agoragentic-micro-ecf@latest index . --output-dir .micro-ecf\nnpx agoragentic-micro-ecf@latest build-packet --policy .micro-ecf/policy.json --source-map .micro-ecf/source-map.json --output-dir .micro-ecf\nnpx agoragentic-micro-ecf@latest export --agent-os --policy .micro-ecf/policy.json --output .micro-ecf/harness-export.json\n```\n\nExpected output: `ECF.md`, `.micro-ecf/source-map.json`, `.micro-ecf/policy-summary.json`, `.micro-ecf/context-packet.json`, and `.micro-ecf/harness-export.json`.\n\nProof demo: [`.env` stays blocked while allowed sources keep citations](examples/secret-block-proof.md).\n\nMicro ECF is not a semantic RAG engine, vector store, hosted answer pipeline, or Full ECF runtime. It tells an agent what context is allowed, where it came from, what is blocked, and what can be exported into an Agent OS deployment preview.\n\nMicro ECF runs locally and does not require Agoragentic Cloud.\n\n\u003cp align=\"center\"\u003e\n  \u003cimg src=\"assets/micro-ecf-hero.png\" alt=\"Micro ECF - local context wedge for safer agents\" width=\"100%\" /\u003e\n\u003c/p\u003e\n\nUse `agoragentic-micro-ecf` when you want lightweight local policy/source artifacts before hosted deployment. Use `agoragentic-ecf-core` when you need richer self-hosted context governance.\n\n\u003cp align=\"center\"\u003e\n  \u003cimg src=\"assets/micro-ecf-architecture.png\" alt=\"Micro ECF architecture diagram showing local inputs, bounded context artifacts, blocked secret paths, and Agent OS preview outputs\" width=\"100%\" /\u003e\n\u003c/p\u003e\n\n## Agoragentic family\n\n| Repo / package | What it is |\n|---|---|\n| **[agoragentic-micro-ecf](https://github.com/rhein1/agoragentic-micro-ecf) (this repo)** | **Open local context wedge (npm `agoragentic-micro-ecf`)** |\n| [agoragentic-ecf-core](https://github.com/rhein1/agoragentic-ecf-core) | Self-hosted context-governance runtime (npm `agoragentic-ecf-core`) |\n| [agoragentic-integrations](https://github.com/rhein1/agoragentic-integrations) | 50+ agent-framework adapters + SDK \u0026 MCP server (npm `agoragentic-mcp`) |\n| [agoragentic-premortem-golden-loop](https://github.com/rhein1/agoragentic-premortem-golden-loop) | Pre-launch release-readiness CLI (npm `agoragentic-premortem-golden-loop`) |\n| [agoragentic-summarizer-agent](https://github.com/rhein1/agoragentic-summarizer-agent) | Python example: route `summarize` via `execute()` |\n| [agoragentic-openai-agents-example](https://github.com/rhein1/agoragentic-openai-agents-example) | OpenAI Agents SDK marketplace example |\n\nHome: **[agoragentic.com](https://agoragentic.com)** · all packages: `npm view \u003cname\u003e`\n\n## What This Means For Builders\n\nWhen a builder installs Micro ECF on a codebase, the repo gains a persistent AI work boundary. Future agents can read the generated `AGENTS.md`, `ECF.md`, `.micro-ecf/context-packet.json`, `.micro-ecf/policy-summary.json`, and `.micro-ecf/source-map.json` before making changes.\n\nThat gives the builder:\n\n- continuity across Codex, Cursor, Claude, Gemini, and other IDE-agent sessions\n- an explicit list of allowed and blocked local sources\n- citation-ready context packets for reviewing why an agent used a source\n- local tool, budget, approval, memory, and swarm boundaries\n- resident worklog, docs-sync plan, and handoff artifacts for long goals\n- an Agent OS Harness export when the builder wants a no-spend hosted preview\n\nMicro ECF does not replace source-code inspection. It gives agents a durable starting contract and local governance packet so they know what to inspect, what not to expose, and what should require owner review.\n\nThe resident memory layer adds continuity for work that spans multiple chats or IDE restarts. It records the active goal, checkpoints, commits, validation, unfinished work, docs-impact plan, and next prompt in local `.micro-ecf/` files that a future agent can inspect. This is not cloud memory or hidden agent state; it is a local file ledger the builder can review, edit, or delete.\n\n## Agent OS Upgrade Path\n\nUse this guide when you want the shortest path from local Micro ECF artifacts to hosted Agent OS readiness:\n\n- [Micro ECF To Agent OS Guide](./MICRO_ECF_TO_AGENT_OS.md)\n- [When to upgrade from Micro ECF to ECF Core](./ECF_CORE_UPGRADE.md)\n- [Roadmap overview image](./assets/roadmap/roadmap-overview.png)\n\n![Micro ECF to Agent OS roadmap](assets/roadmap/roadmap-overview.png)\n\n## Product Boundary\n\nMicro ECF is not Full ECF.\n\nUse this product rule everywhere:\n\n```text\nMicro ECF is the local context wedge.\nECF Core is the open-source self-hosted context-governance runtime.\nAgent OS is the deployment product.\nFull ECF is private/internal infrastructure.\n```\n\nArchitecture rule:\n\n```text\nMicro ECF may prepare context for Agent OS, but it must not contain the private runtime,\nsettlement, trust-ranking, or enterprise governance internals that make Agoragentic defensible.\n```\n\nLearning memory follows the same boundary. It may rank, block, route, summarize, or recommend review guidance, but it must never auto-approve, auto-dispatch, spend funds, mutate code, deploy, change secrets, publish marketplace listings, or bypass human/ECF approval.\n\n## What Micro ECF Does\n\nMicro ECF helps a builder answer:\n\n```text\nGiven the context my tools already have or can locally summarize, what is this agent\nallowed to know, cite, use, act on, and export into an Agent OS deployment preview?\n```\n\nCore capabilities:\n\n- bounded local source inventory and summarization\n- context packet generation from source summaries/provenance\n- citation/source maps for allowed local artifacts\n- policy summaries\n- tool/context allowlists\n- small workflow maps\n- optional context-provider declarations for RAG/code-graph/MCP systems\n- pre/post-action governance inputs for the Consequences Engine\n- review-only learning-memory boundary metadata\n- deployment-intent files\n- Agent OS Harness export\n- optional local MCP server\n\nGood inputs:\n\n- markdown/docs\n- small repos\n- local files\n- SQLite files and schema/data summaries\n- small Postgres/MySQL exports\n- API docs\n- agent configs\n- test harnesses\n- local policy files\n\nGenerated outputs:\n\n```text\nECF.md\n.micro-ecf/context-packet.json\n.micro-ecf/policy-summary.json\n.micro-ecf/source-map.json\n.micro-ecf/harness-export.json\n.micro-ecf/deployment-preview.json\n.micro-ecf/resident-status.json\n.micro-ecf/context-pack.json\n.micro-ecf/worklog/current.json\n.micro-ecf/worklog/history.jsonl\n.micro-ecf/worklog/checkpoints.jsonl\n.micro-ecf/worklog/latest-summary.md\n.micro-ecf/docs-sync-plan.json\n.micro-ecf/handoff.json\n.micro-ecf/handoff.md\n.micro-ecf/next-session.md\nAGENTS.md\nMICRO_ECF_LLM_BOOTSTRAP.md\n```\n\n## What A Context Packet Is\n\nA Micro ECF context packet is a governance artifact, not a retrieved-answer bundle.\n\nIt contains:\n\n- source IDs, paths, hashes, summaries, citation IDs, and provenance\n- allowed and blocked context classes\n- export boundaries such as `raw_content_exported=false`\n- references that Agent OS or an IDE assistant can use to inspect the real source files\n\nIt does not contain:\n\n- embeddings\n- vector indexes\n- semantic search results\n- model-generated answers\n- raw secret or private-file contents\n- Full ECF private context graph internals\n\nUse direct source reads, your own RAG, GitNexus, or another MCP/context provider as the source of truth for deep retrieval. Use Micro ECF to govern what those systems may expose or act on.\n\n## ECF.md\n\n`ECF.md` is the persistent agent-readable Micro ECF contract for a local project. It follows the same practical pattern as other agent-readable project contracts: machine-readable front matter plus human-readable rationale.\n\nUse it when a new Codex, Cursor, Claude, Gemini, database, or IDE agent conversation needs to know:\n\n- what Micro ECF is doing in this repo\n- which sources are allowed\n- which sources are blocked\n- how to verify Micro ECF is installed\n- when to use `.micro-ecf/*` artifacts\n- when to export an Agent OS Harness packet\n\nCommands:\n\n```bash\nmicro-ecf lint ECF.md\nmicro-ecf diff ECF.md ECF-next.md\nmicro-ecf spec\n```\n\n## What Micro ECF Does Not Include\n\nDo not add these to Micro ECF:\n\n- semantic/vector retrieval engine\n- hosted RAG answer path\n- embedding store or model-backed reranker\n- Full ECF private context graph internals\n- tenant isolation runtime\n- enterprise connector architecture\n- enterprise audit-log internals\n- marketplace ranking, trust, or fraud internals\n- router provider-selection internals\n- wallet settlement internals\n- x402 settlement executor internals\n- hosted provisioning code\n- private connectors\n- secrets broker\n- operator prompts\n- customer-control evidence tooling\n- internal policy scoring for enterprise approvals\n\nMicro ECF can produce inputs and governance envelopes for those systems. It should not implement them.\n\n## One-Command Setup\n\nIf you are using an IDE LLM, paste this GitHub folder link into the chat:\n\n```text\nhttps://github.com/rhein1/agoragentic-micro-ecf\n```\n\nThen ask it to follow [`LLM_INSTALL.md`](./LLM_INSTALL.md). The required flow is:\n\n```bash\nmicro-ecf plan --dir .\n# show the plan and wait for explicit approval\nmicro-ecf install --dir . --yes\n```\n\n`plan` is read-only. `install` without `--yes` refuses to write files and returns the approval plan.\n\nImportant: installing Micro ECF creates persistent repo artifacts. It does not automatically inject hidden context into every future LLM conversation.\n\nFor future conversations, use one of three handoff paths:\n\n- Compatible IDE agents should auto-read `AGENTS.md`, then inspect `.micro-ecf/policy-summary.json`, `.micro-ecf/context-packet.json`, and `.micro-ecf/source-map.json`.\n- Any other LLM chat should receive `MICRO_ECF_LLM_BOOTSTRAP.md` as a pasted or attached bootstrap file at the start of the conversation.\n- IDEs that support persistent MCP tools can run `micro-ecf serve-mcp --root .micro-ecf` and configure that server once.\n\nFor the full after-install checklist, see [`POST_INSTALL.md`](./POST_INSTALL.md).\n\nFrom this repo:\n\n```bash\nnpm test\nnode bin/micro-ecf.mjs plan --dir ../my-agent\nnode bin/micro-ecf.mjs install --dir ../my-agent --yes\n```\n\nFrom npm:\n\n```bash\nnpx agoragentic-micro-ecf@latest explain\nnpx agoragentic-micro-ecf@latest plan --dir .\nnpx agoragentic-micro-ecf@latest install --dir . --yes\n```\n\nThe binary is intentionally simple:\n\n```bash\nmicro-ecf init\nmicro-ecf scan\nmicro-ecf doctor\nmicro-ecf lint ECF.md\nmicro-ecf plan\nmicro-ecf install --yes\nmicro-ecf index ./docs\nmicro-ecf build-packet\nmicro-ecf export --agent-os\nmicro-ecf search --query \"...\"\nmicro-ecf validate-policy\nmicro-ecf serve-mcp\nmicro-ecf status --write\nmicro-ecf context-pack --write\nmicro-ecf resident status\nmicro-ecf resident refresh\nmicro-ecf mcp-config --target codex --write\nmicro-ecf worklog begin --goal \"...\"\nmicro-ecf worklog checkpoint --summary \"...\"\nmicro-ecf worklog finish --summary \"...\"\nmicro-ecf docs-sync plan\nmicro-ecf handoff --write\n```\n\n## Resident Work Memory\n\nUse the resident worklog when a goal spans multiple IDE or Codex conversations:\n\n```bash\nmicro-ecf worklog begin --goal \"Implement local proof runner\"\nmicro-ecf worklog checkpoint --summary \"CLI and receipt verifier are drafted\" --validation \"npm test\"\nmicro-ecf worklog finish --summary \"Committed local proof runner\" --commit abc123 --tests \"npm test\" --next-prompt \"Harden receipt verification\"\nmicro-ecf docs-sync plan --dir .\nmicro-ecf handoff --write\n```\n\nThe worklog and handoff artifacts are local-only. `docs-sync plan` proposes documentation updates but does not edit docs. Micro ECF will not auto-edit documentation unless a future explicit apply command is added and intentionally run.\n\nFor builders, the resident files answer five practical questions at the start of the next session:\n\n- What goal was active?\n- What changed and which files were involved?\n- Which validation ran?\n- Which docs probably need updates?\n- What exact next prompt should the next agent continue from?\n\nFor a single local refresh before closing an IDE or Codex session, use:\n\n```bash\nmicro-ecf resident refresh --dir .\n```\n\n`resident refresh` writes only `.micro-ecf/` resident artifacts: `resident-status.json`, `context-pack.json`, `docs-sync-plan.json`, `handoff.md`, `handoff.json`, and `next-session.md`. It does not deploy, spend, mutate wallets, settle x402, publish marketplace listings, provision hosted runtime, or expose Full ECF private internals.\n\nIf Codex or another IDE supports local MCP tools, `micro-ecf serve-mcp --root .micro-ecf` exposes read-only resident tools for future sessions:\n\n- `micro_ecf.worklog_status`\n- `micro_ecf.handoff`\n- `micro_ecf.work_memory`\n\n## Local Workflow\n\nInitialize a local project:\n\n```bash\nnpx agoragentic-micro-ecf@latest init --dir ./my-agent\n```\n\nVerify the local install and inspect the context boundary without writing:\n\n```bash\nnpx agoragentic-micro-ecf@latest doctor --dir ./my-agent\nnpx agoragentic-micro-ecf@latest scan --dir ./my-agent\n```\n\nIndex bounded local context:\n\n```bash\nnpx agoragentic-micro-ecf@latest index ./my-agent/docs --output-dir ./my-agent/.micro-ecf\n```\n\nBuild local artifacts:\n\n```bash\nnpx agoragentic-micro-ecf@latest build-packet \\\n  --policy ./my-agent/.micro-ecf/policy.json \\\n  --source-map ./my-agent/.micro-ecf/source-map.json \\\n  --output-dir ./my-agent/.micro-ecf\n```\n\nExport an Agent OS Harness packet:\n\n```bash\nnpx agoragentic-micro-ecf@latest export --agent-os \\\n  --policy ./my-agent/.micro-ecf/policy.json \\\n  --output ./my-agent/.micro-ecf/harness-export.json\n```\n\nThen hand it to hosted Agent OS:\n\n```bash\nAGORAGENTIC_API_KEY=amk_your_key npx agoragentic-os@latest deploy readiness --file ./my-agent/.micro-ecf/harness-export.json\nAGORAGENTIC_API_KEY=amk_your_key npx agoragentic-os@latest deploy preview --file ./my-agent/.micro-ecf/harness-export.json\nAGORAGENTIC_API_KEY=amk_your_key npx agoragentic-os@latest deploy create --file ./my-agent/.micro-ecf/harness-export.json\n```\n\nThe export itself is no-spend and non-provisioning. `readiness` and `preview` are no-spend checks. `deploy create` records a hosted deployment request; funding, runtime provisioning, public API exposure, marketplace selling, and x402 monetization remain separate approval-gated steps.\n\n## Legacy Export Helper\n\nThe original helper remains available:\n\n```bash\nnode export-agent-os-harness.mjs \\\n  --policy policy.example.json \\\n  --output ./agent-os-harness.packet.json\n```\n\nUse the CLI for full local context artifacts. Use the helper when you only need a Harness packet from a policy file.\n\n## Local MCP Server\n\nMicro ECF can run as a local stdio MCP server:\n\n```bash\nmicro-ecf serve-mcp --root .micro-ecf\n```\n\nTools:\n\n- `micro_ecf.search_context`\n- `micro_ecf.get_source`\n- `micro_ecf.get_policy`\n- `micro_ecf.build_packet`\n- `micro_ecf.export_agent_os_harness`\n\nThe MCP server reads and writes local `.micro-ecf` artifacts only. It does not call Agoragentic Cloud.\n\n## Context Providers\n\nMicro ECF can attach optional context providers for pre-action impact review. A provider brings its own retrieval, graph, or database engine; Micro ECF records the provider contract, policy boundary, and evidence shape so Agent OS can evaluate blast radius before an agent acts.\n\nFull guide: [`PROVIDER_WRAPPING.md`](./PROVIDER_WRAPPING.md).\n\nFramework guide: [`FRAMEWORKS.md`](./FRAMEWORKS.md).\n\nEvidence/eval backlog: [`AGENT_OS_EVIDENCE_EVAL_BACKLOG.md`](./AGENT_OS_EVIDENCE_EVAL_BACKLOG.md).\n\nSupported provider types:\n\n| Type | Description |\n|------|-------------|\n| `code_graph` | Codebase structural awareness: functions, imports, call chains, dependencies |\n| `retrieval_context` | RAG, document retrieval, database schema/context, or other context engines that return cited evidence |\n| `tool_graph` | Tool and API dependency graph |\n| `policy_graph` | Governance and compliance policy relationships |\n| `workflow_graph` | Multi-step workflow and process dependencies |\n| `receipt_graph` | Transaction and receipt chain relationships |\n| `marketplace_graph` | Marketplace listing and seller dependency graph |\n| `enterprise_context_graph` | Reserved for Full ECF / enterprise deployments, not local Micro ECF internals |\n\n### Existing RAG As `retrieval_context`\n\nIf you already have RAG, keep it. Configure it as a provider:\n\n```json\n{\n  \"context_providers\": [\n    {\n      \"provider_id\": \"ctx_local_rag_docs\",\n      \"type\": \"retrieval_context\",\n      \"provider\": \"local_rag\",\n      \"mode\": \"local_mcp\",\n      \"enabled\": true,\n      \"scope\": \"docs_and_repo\",\n      \"capabilities\": [\"query\", \"retrieve\", \"cite\"],\n      \"required\": false,\n      \"required_for_action_classes\": [\"read_only\", \"code_change\"],\n      \"mcp\": {\n        \"server\": \"local-rag\",\n        \"transport\": \"stdio\"\n      }\n    }\n  ]\n}\n```\n\nYour RAG provider owns retrieval. Micro ECF owns the policy envelope: allowed sources, blocked sources, citation requirements, budget/action gates, and whether an action should fail closed if the provider is unavailable.\n\n### GitNexus As Optional `code_graph`\n\nGitNexus can be used as an optional local `code_graph` provider. Treat it as a provider pattern, not a dependency or rebrand.\n\n```json\n{\n  \"context_providers\": [\n    {\n      \"provider_id\": \"ctx_gitnexus_local\",\n      \"type\": \"code_graph\",\n      \"provider\": \"gitnexus\",\n      \"name\": \"GitNexus\",\n      \"mode\": \"local_mcp\",\n      \"status\": \"available\",\n      \"enabled\": true,\n      \"scope\": \"workspace\",\n      \"capabilities\": [\"impact\", \"context\", \"query\", \"detect_changes\", \"generate_map\"],\n      \"required\": false,\n      \"required_for_action_classes\": [\"code_change\"],\n      \"mcp\": {\n        \"server\": \"gitnexus\",\n        \"transport\": \"stdio\"\n      }\n    }\n  ]\n}\n```\n\nIf no provider is configured or reachable, Agent OS falls back to standard policy/consequence review. Micro ECF does not silently replace the provider with a hidden RAG system.\n\n## How It Connects To Agent OS\n\nFunnel:\n\n```text\n1. Builder installs Micro ECF locally.\n2. Builder points it at repo/docs/db.\n3. Micro ECF builds source maps, policy summaries, and context packets from allowed local summaries/provenance.\n4. Builder sees what the agent can safely know, cite, use, and which external context providers may be consulted.\n5. Micro ECF exports Agent OS Harness files.\n6. Builder previews deployment on Agoragentic.\n7. If they want runtime, wallets, APIs, receipts, marketplace, or x402 monetization, they move to Agent OS.\n8. If they outgrow static local artifacts but still do not need hosted deployment, they move to ECF Core.\n9. Full ECF remains private/internal infrastructure and is not included in Micro ECF or ECF Core.\n```\n\nCanonical hosted contracts:\n\n- `https://agoragentic.com/agent-os-harness.json`\n- `https://agoragentic.com/schema/agent-os-harness.v1.json`\n- `https://agoragentic.com/schema/micro-ecf-policy.v1.json`\n- `https://agoragentic.com/agent-os/launch/`\n- `https://agoragentic.com/agent-os/deployments/`\n\n## Schemas\n\nLocal schemas:\n\n- `schema/micro-ecf-policy.v1.json`\n- `schema/agent-os-harness.v1.json`\n- `schema/context-packet.schema.json`\n- `schema/source-map.schema.json`\n- `schema/policy-summary.schema.json`\n- `schema/deployment-preview.schema.json`\n- `schema/harness-export.schema.json`\n\n## Publishing\n\nMicro ECF should be published through npm Trusted Publishing. Do not add long-lived npm write tokens to GitHub Actions.\n\nSee [`TRUSTED_PUBLISHING.md`](./TRUSTED_PUBLISHING.md).\n\n## License\n\nMicro ECF is licensed under Apache-2.0. The wider integrations repository may contain other adapters under the repository-level license; this folder carries its own package license boundary.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frhein1%2Fagoragentic-micro-ecf","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Frhein1%2Fagoragentic-micro-ecf","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frhein1%2Fagoragentic-micro-ecf/lists"}