A

Delivery structure

1 specs, 1 requirements, 1 with no code mapped
Knuckles-Team/kafka-mcpSpec delivery
Specs (1)
  • CONN-KAFKA-MCP-CONNECTOR-CONTENT1
Records not done
  • Requirementsall slices in all specs1
  • Requirements not donenot VERIFIED0
  • Specs not donewhole specs only0

Each spec shows its requirement count. Panel J lists every record.

B

Delivery states

count of total

Requirements (1)

VERIFIED (verified)1 of 1 requirements

Specs (1)

VERIFIED (verified)1 of 1 specs

Each bar shows one state against all records of the same kind.

Percentages count current rows. Done means VERIFIED.

C

State definitions

delivery_state
StateDefinition
SPECIFIEDThe requirement is written. No code for it is on the default branch.
LANDEDA commit that carries its ID in a Spec trailer is on the default branch.
VERIFIEDIt is LANDED and a test bound to its ID exists.

A spec state is the lowest state of its rows. Done means VERIFIED.

Invalid state: 0

D

Specifications

specs/*/status.json
Spec / titleReq.LandedDoneSpec stateCode references
CONN-KAFKA-MCP-CONNECTOR-CONTENTCONN-KAFKA-MCP-CONNECTOR-CONTENT — The connector serves its packaged content11/11✓ VERIFIEDspec.md documentation: file exists; coverage not verified
requirements.md documentation: file exists; coverage not verified

Landed counts LANDED and VERIFIED requirements. Done counts VERIFIED requirements only.

The spec state comes from the spec status file only.

U

Spec architecture

repository / component packages

Packages group specs by repository and declared component. Unassigned means no component was declared. Code links do not prove coverage. Mermaid source.

Knuckles-Team/kafka-mcp / Unassigned (1)
Knuckles-Team/kafka-mcp / Unassigned (1)CONN-KAFKA-MCP-CONNECTOR-CONTENT

CONN-KAFKA-MCP-CONNECTOR-CONTENT: no plan diagram declared.

R

Spec relationships

declared dependencies and references

Depends on means a declared prerequisite. Extends and references do not imply prerequisite order. Shared code never creates dependencies. External targets are source declarations, not verified delivery.

Knuckles-Team/kafka-mcp / Unassigned
SpecRelationshipTargetEvidence
CONN-KAFKA-MCP-CONNECTOR-CONTENTNo relationships declared; dependencies unknown
G

Open issues and pull requests

open at capture

Issues

0 open at capture.

    Pull Requests

    0 open at capture.

      The build reads GitHub one time. This page makes no live API requests.

      J

      Record inventory

      2 records

      Each status file gives one spec row. Each requirement gives one more row. A record without a valid state shows INVALID. Expand a Definition to read the canonical requirement and verification text.

      All documented records (2 rows)
      ID / sourceKindParentStateCommit / test evidence
      CONN-KAFKA-MCP-CONNECTOR-CONTENT
      CONN-KAFKA-MCP-CONNECTOR-CONTENT — The connector serves its packaged content      		specNoneVERIFIEDNo recorded commit/test evidence
      CONN-KAFKA-MCP-CONNECTOR-CONTENT-R001
      Default content
      Definition — CONN-KAFKA-MCP-CONNECTOR-CONTENT / CONN-KAFKA-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source
      **Default content.** `pyproject.toml` declares `kafka-mcp` as the single `agent_connector_sdk.connector` entry point. The server lists the packaged `skill://` and `ontology://` resources and the packaged prompts with no `content=` argument. Proving test: `tests/test_default_content_surfaces.py`. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt.
      		requirementCONN-KAFKA-MCP-CONNECTOR-CONTENTVERIFIED44deee600cda
      faee607795b6
      tests/test_default_content_surfaces.py:15
      TitleSpec delivery: kafka-mcp
      RepositoryKnuckles-Team/kafka-mcp
      Commit6ce93b724850
      Captured (UTC)2026-10-26T23:24:53
      Snapshotsnapshot.json (v1)
      Sourcespecs/*/status.json
      Sheet1 of 1