CAPABILITY / EVIDENCE MAP

Every capability points at a published case.

What this answers is "have you actually done this." The left column is capabilities, the right is cases — every edge points at something that case’s own record already states. Nothing new is claimed here.

Prototype · covers 3 cases
Left column: capabilities — click to see the evidence
Right column: published cases — click through to the case
Each line: one piece of evidence stated in that case

Capability-to-evidence map

Evidence · 3 items

System architecture and abstractions

Setting the core abstraction and boundaries a system keeps growing on.

Click another capability on the left to switch · click again to reset
  1. Rotifer ProtocolREC-001A "gene" abstraction defining how capabilities compose, compete, and evolve.View the case →
  2. AtlaxyREC-002Map experience, API, agent worker, shared schema, and snapshots in one system.View the case →
  3. RepoAssureREC-003A local-first CLI/MCP architecture chaining analysis through reporting.View the case →
System architecture and abstractions3 evidence items

Setting the core abstraction and boundaries a system keeps growing on.

  1. Rotifer ProtocolREC-001A "gene" abstraction defining how capabilities compose, compete, and evolve.View the case →
  2. AtlaxyREC-002Map experience, API, agent worker, shared schema, and snapshots in one system.View the case →
  3. RepoAssureREC-003A local-first CLI/MCP architecture chaining analysis through reporting.View the case →
Agent and MCP integration3 evidence items

Systems usable by people and agents alike: MCP servers, workers, machine-readable interfaces.

  1. Rotifer ProtocolREC-001The MCP server @rotifer/mcp-server 0.17.0 is published publicly on npm.View the case →
  2. AtlaxyREC-002Web, API, and MCP entry points, plus an agent worker — all checkable in the project record.View the case →
  3. RepoAssureREC-003The CLI/MCP capability in the local repo actually runs — it isn't a design mockup.View the case →
Web product and API delivery1 evidence item

Shipping a system as a reachable product: front end, public API, a released version.

  1. AtlaxyREC-002Public Beta v0 is live, with four working entry points: Web, API, State of AI, and Rising Radar.View the case →
Developer tooling and CLI2 evidence items

Tools for the development process itself: command line, local-first, embeddable.

  1. Rotifer ProtocolREC-001The @rotifer/playground 0.21.1 development environment is published with native binaries for four platforms.View the case →
  2. RepoAssureREC-003A local-first CLI/MCP tool producing repair handover contracts and delivery material.View the case →
Automated acceptance and quality1 evidence item

Turning "is it deliverable" into runnable checks: browser exploration, generated tests, recorded evidence.

  1. RepoAssureREC-003Browser exploration, security-evidence import, and a repair handover contract — all three are built.View the case →
Data pipelines and snapshots1 evidence item

Turning continuously changing external data into queryable, versioned product content.

  1. AtlaxyREC-002A shared schema and data snapshots are part of that product system.View the case →
0Capabilities
0Published cases
0Evidence edges, each traceable to a sentence in its case
The map only reorganizes claims the cases already make.See all cases →