{
  "markdown": "<div align=\"center\">\n  <img src=\"assets/logo.svg\" alt=\"TMCP logo\" width=\"96\" height=\"96\" />\n  <h1>TMCP</h1>\n  <p><strong>Slash commands are manual imports. TMCP is the compiler.</strong></p>\n</div>\n\nTMCP turns scattered agent instructions into task-specific operating packets. The user describes the work in natural language. TMCP infers task identity, compiles the strongest current packet from skills/rules/evidence, recompiles as the work changes, and leaves an audit trail.\n\nSkill names are provenance, not the user interface. Power users can still force a route; the default is natural prompting.\n\nTMCP runs standalone from a repo checkout, copied plugin package, Codex plugin cache, Claude plugin cache, or any MCP host that can launch the bundled Node entrypoint. The former AIOS adapter is deprecated and disabled by default; `AIOS_ROOT` alone no longer enables it.\n\nSee [docs/ADAPTIVE_PACKET_RUNTIME.md](docs/ADAPTIVE_PACKET_RUNTIME.md) for the adaptive packet runtime design.\n\n## Quickstart\n\nFrom a TMCP checkout or plugin root:\n\n```bash\nnode scripts/tmcp_launcher.mjs doctor\nnode scripts/tmcp_launcher.mjs status\nnode scripts/tmcp_launcher.mjs compose-packet \"Improve this agent run\" --project-path . --phase start\nnode scripts/tmcp_launcher.mjs harvest skills --limit 5 --no-write-artifacts\nnode scripts/tmcp_launcher.mjs recommend skills --candidate-workflows release_readiness --candidate-workflows developer_experience --min-confidence 0.1 --compose --no-write-artifacts\n```\n\nWith no arguments, the same launcher starts the MCP stdio server:\n\n```bash\nnode scripts/tmcp_launcher.mjs\n```\n\n## Install Layouts\n\n- Skill-only install: copy `skills/tmcp` into a skills directory. Use the skill for routing and manual packet synthesis unless the host also exposes the bundled launcher.\n- Repo checkout: clone the repo and run `node scripts/tmcp_launcher.mjs doctor` from the checkout root.\n- Codex plugin cache: install as a Codex plugin; MCP config launches relative `scripts/tmcp_launcher.mjs` from the plugin root.\n- Shared local runtime: install a verified archive with `scripts/tmcp_runtime.mjs` so all agent hosts use one pinned active release with offline rollback. See [Central runtime](docs/CENTRAL_RUNTIME.md).\n- Deprecated AIOS compatibility: requires both `TMCP_ENABLE_DEPRECATED_AIOS_ADAPTER=1` and `AIOS_ROOT`; new installations should use standalone TMCP.\n\nClaude Desktop users can add the launcher as a local stdio MCP server. See [docs/CLAUDE_DESKTOP.md](docs/CLAUDE_DESKTOP.md).\n\n## Stability Scopes\n\nTMCP labels three independent surfaces:\n\n- **Skill packages:** `tmcp`, `skill-harvest`, `workflow-recommendation`, `release-readiness`, and `dx-audit` are stable routing packages.\n- **Curated workflow templates:** `release-readiness` and `dx-audit` are the stable templates in the recommendation catalog.\n- **MCP tool contracts:** `doctor`, `status`, `explain`, `compose-packet`, and `runtime-next` are stable. Harvest, evaluation, recommendation, promotion, receipt, and expert-rubric tools remain experimental.\n\nExperimental templates and tools remain shipped and callable. They are labeled experimental in their own outputs and frontmatter so users do not confuse a stable package route with a stable tool contract or curated template.\n\nExperimental workflows include UI rubric, security/privacy, test strategy, adaptive workflow pack, custom rubric generation, routing policy, skill gap analysis, incident postmortem, architecture decision, migration readiness, agent handoff, PR risk, performance readiness, data integrity, public-sector readiness, and repo behavior spec loop.\n\n## Tools\n\n| Tool | Purpose |\n| --- | --- |\n| `tmcp_doctor` | Check first-run readiness and supported install layouts. |\n| `tmcp_status` | Report standalone capability and optional AIOS adapter status. |\n| `tmcp_explain` | Compile a task-specific TMCP packet. |\n| `tmcp_compose_packet` | Compile a task/phase operating packet with `task_identity`, `packet_markdown`, and provenance. |\n| `tmcp_runtime_next` | Return packet deltas or a full recompiled packet (`output_mode: full`) after runtime evidence changes. |\n| `tmcp_record_receipt` | Write an advisory run receipt after verification or outcome on a secure-persistence host. |\n| `tmcp_harvest_skills` | Harvest local skills, instructions, rules, docs, and workflows into source nodes. |\n| `tmcp_evaluate_skills` | Create or score a skill-evaluation plan from full `SKILL.md` inputs. |\n| `tmcp_recommend_workflows` | Recommend stable or experimental workflows from harvested evidence, with stability metadata. |\n| `tmcp_promote_harvest` | Explicitly promote reviewed harvest signals into durable source-to-atom and atom-to-workflow graph artifacts. |\n| `expert_rubric_review_plan` | Produce an expertise packet, scored rubric, evidence audit, remediation plan, and verification expectations. |\n\n## Safety\n\nHarvest redacts sensitive-looking values and secret-like provenance paths by default and treats harvested instructions as untrusted text. Default harvest behavior excludes `.env*`, credentials, tokens, browser profiles, private caches, dependency trees, build outputs, VCS data, and generated TMCP/AIOS artifacts. It does not follow source symlinks unless `follow_symlinks` is explicitly enabled; enabled links must still resolve inside the selected source root.\n\nOn hosts with secure descriptor-relative filesystem operations, harvest artifacts\nare written as one staged, atomic bundle through a symlink-safe destination.\nLeave `output_dir` unset for a unique `.tmcp/harvest-*` directory, or provide an\noutput directory that is new or empty.\n\nSkill evaluation accepts explicit regular `SKILL.md` inputs, can confine them to a supplied project root, and redacts source, plan, and evidence values before deriving reports. Its initial plan artifact is a staged bundle in a new or empty directory; evidence scoring may safely add its report to that same directory.\n\nArtifact persistence is deliberately unavailable where those secure filesystem\noperations do not exist. `doctor` and `status` report the capability; use\n`--no-write-artifacts` for portable analysis and see\n[Compatibility](docs/COMPATIBILITY.md#secure-artifact-persistence) for the\nboundary.\n\n`tmcp_record_receipt` has no non-persisting preview because the receipt is the\nartifact itself. Run it only when `status` reports artifact persistence\navailable.\n\nPacket sessions are equally explicit: `compose-packet --session-id` writes one\nredacted, project-local latest-packet record only when secure persistence is\navailable. They are for a single serialized run, not a global history or\ncoordination service. See [the CLI session contract](docs/CLI.md#packet-sessions).\n\nIf a harvested source tries to override system, developer, or user instructions, TMCP reports a warning. See [SECURITY.md](SECURITY.md).\n\n## Examples\n\nHarvest a local skills folder:\n\n```bash\nnode scripts/tmcp_launcher.mjs harvest ./skills --objective \"Harvest reusable skill behavior\" --limit 20 --no-write-artifacts\n```\n\nRecommend workflows for a project:\n\n```bash\nnode scripts/tmcp_launcher.mjs recommend . --candidate-workflows release_readiness --candidate-workflows developer_experience --min-confidence 0.1 --compose --no-write-artifacts\n```\n\nCompose a current-task packet and recompile during the run. This session flow\nrequires `status` to report artifact persistence available:\n\n```bash\nnode scripts/tmcp_launcher.mjs compose-packet \\\n  \"Redesign these pages. Make them visually striking, interactive, modern, motion-rich, and production-ready.\" \\\n  --project-path \"$PWD\" --phase start --session-id redesign-run\n\nnode scripts/tmcp_launcher.mjs recompile-packet \\\n  \"Redesign these pages...\" \\\n  --project-path \"$PWD\" \\\n  --current-phase runtime \\\n  --session-id redesign-run \\\n  --files-changed app/page.tsx\n\nnode scripts/tmcp_launcher.mjs record-receipt packet-123 --activated-atoms ui-browser-verification --outcome passed\n```\n\nWhen session persistence is unavailable, preserve the compatibility path by\npassing the prior composed JSON inline through `--previous-packet` instead.\n\nLegacy delta-only runtime routing:\n\n```bash\nnode scripts/tmcp_launcher.mjs compose-packet \"Fix the dashboard UI bug\" --project-path . --phase start\nnode scripts/tmcp_launcher.mjs runtime-next \"Fix the dashboard UI bug\" --current-phase verification --files-changed app/page.tsx --failures \"vitest failed\"\nnode scripts/tmcp_launcher.mjs record-receipt packet-123 --activated-atoms ui-browser-verification --outcome passed\n```\n\nPromote reviewed harvest signals into durable routing artifacts:\n\n```bash\nnode scripts/tmcp_launcher.mjs promote-harvest . --selected-workflows release_readiness_workflow --output-dir .tmcp/promoted-harvests/release-readiness\n```\n\nOn secure-persistence hosts, promotions also persist a redacted advisory graph\nunder `TMCP_HOME/promoted-harvests/<opaque-promotion-key>/`, or\n`~/.tmcp/promoted-harvests/<opaque-promotion-key>/` when `TMCP_HOME` is unset.\nReceipts live under `TMCP_HOME/receipts/<yyyy-mm>/`.\nGlobal cache content is advisory and cannot override system, developer, user, or\nproject instructions.\nPacket composition and runtime routing do not read that cache unless the caller\nexplicitly passes `--cache-policy global`; their default policy is `none`.\n\nRun an expert rubric review from evidence snippets:\n\n```bash\nnode scripts/tmcp_launcher.mjs review-plan \"Review release portability\" \\\n  --project-path . \\\n  --evidence-json '[{\"dimension_id\":\"source_grounding\",\"severity\":\"warning\",\"summary\":\"Release claims need fresh package evidence.\",\"evidence\":[\"python3 scripts/check_release_package.py .\"],\"recommended_fix\":\"Run and cite the release package check before publishing.\"}]' \\\n  --no-write-artifacts\n```\n\nMore examples live in [examples](examples). Developer onboarding and release readiness exercise stable curated templates; skill-harvest and recommendation examples remain available through experimental tool contracts.\n\n## Validation\n\nBefore release:\n\n```bash\npython3 -m unittest discover -s tests\npython3 scripts/release_package_compile.py .\nnode --check scripts/tmcp_launcher.mjs\npython3 scripts/check_contracts.py .\npython3 scripts/check_install.py .\npython3 scripts/check_release_package.py . --verify-reproducible\n```\n\nThe release package check builds from a clean, reviewed Git revision rather than\nthe working directory. It ships only an explicit allowlist of committed files,\nrejects unsafe paths, symlinks, and secret-like content, then emits a\ndeterministic RELEASE_MANIFEST.json plus archive digest. The CI release gate\nrepeats the build from the same Git tree and requires both digests to match. It also validates\nfrontmatter, hardcoded local paths, private example names, links,\nextracted-package install shape, doctor, sample harvest, sample workflow\nrecommendation, sample expert rubric planning, composition/runtime/receipt smoke\ncoverage, and stable/experimental workflow labeling.\nIt is a DOI blocker until existing absolute user paths in release evidence docs are redacted or normalized.\n\n## DOI-Ready Research Release\n\nTMCP is prepared as an independent software-methods artifact. See\n[RESEARCH_READY.md](RESEARCH_READY.md) and\n[docs/release-notes/v0.3.3-doi.md](docs/release-notes/v0.3.3-doi.md) for the\ncitable artifact boundary, validation path, data-availability policy, and claim\nlimits.\n\n## References\n\n- [Quickstart](docs/QUICKSTART.md)\n- [CLI](docs/CLI.md)\n- [Install and package check](docs/INSTALL.md)\n- [Distribution](docs/DISTRIBUTION.md)\n- [Central runtime](docs/CENTRAL_RUNTIME.md)\n- [Packet stability](docs/PACKET_STABILITY.md)\n- [Adaptive packet runtime](docs/ADAPTIVE_PACKET_RUNTIME.md)\n- [Tier One release rubric](docs/TIER_ONE_RELEASE_RUBRIC.md)\n",
  "bytes": 11723,
  "sha": "a4fa2710873f178bd63db99af105da2c28dba1126f7d28e3b6f2aefcf48c04b9",
  "repo_slug": "jakyeamos/tmcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_jakyeamos_tmcp_581c1e3f/readme"
}