- CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT1
- CONN-TECHNITIUM-DNS-MCP1
- Requirementsall slices in all specs2
- Requirements not donenot VERIFIED1
- Specs not donewhole specs only1
Each spec shows its requirement count. Panel J lists every record.
Requirements (2)
Specs (2)
Each bar shows one state against all records of the same kind.
Percentages count current rows. Done means VERIFIED.
| State | Definition |
|---|---|
| SPECIFIED | The requirement is written. No code for it is on the default branch. |
| LANDED | A commit that carries its ID in a Spec trailer is on the default branch. |
| VERIFIED | It 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
| Spec / title | Req. | Landed | Done | Spec state | Code references |
|---|---|---|---|---|---|
| CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENTCONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | 1 | 1/1 | 0 | LANDED | spec.md documentation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified |
| CONN-TECHNITIUM-DNS-MCPCONN-TECHNITIUM-DNS-MCP — Technitium DNS ingestible sources | 1 | 1/1 | 1 | ✓ VERIFIED | ../../tests/test_ingest_sources.py test: file exists; coverage not verified ../../technitium_dns_mcp/ontology/ingest_sources.json implementation: missing source plan.md documentation: file exists; coverage not verified tests/test_ingest_sources.py test: 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.
Packages group specs by repository and declared component. Unassigned means no component was declared. Code links do not prove coverage. Mermaid source.
Knuckles-Team/technitium-dns-mcp / Connector (1)
CONN-TECHNITIUM-DNS-MCP: no plan diagram declared.
Knuckles-Team/technitium-dns-mcp / Unassigned (1)
CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT: no plan diagram declared.
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/technitium-dns-mcp / Connector
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-TECHNITIUM-DNS-MCP | No relationships declared; dependencies unknown | ||
Knuckles-Team/technitium-dns-mcp / Unassigned
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT | No relationships declared; dependencies unknown | ||
Issues
0 open at capture.
Pull Requests
0 open at capture.
The build reads GitHub one time. This page makes no live API requests.
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 (4 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | spec | None | LANDED | No recorded commit/test evidence |
| CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT-R001 Default content Definition — CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT / CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Default content.** `pyproject.toml` declares `technitium-dns-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. | requirement | CONN-TECHNITIUM-DNS-MCP-CONNECTOR-CONTENT | LANDED | ce4e20f8c147 |
| CONN-TECHNITIUM-DNS-MCP CONN-TECHNITIUM-DNS-MCP — Technitium DNS ingestible sources | spec | None | VERIFIED | No recorded commit/test evidence |
| CONN-TECHNITIUM-DNS-MCP-R001 Declare the `zones` source Definition — CONN-TECHNITIUM-DNS-MCP / CONN-TECHNITIUM-DNS-MCP — Technitium DNS ingestible sourcesCanonical requirement and verification source**Declare the `zones` source.** The connector ships `technitium_dns_mcp/ontology/ingest_sources.json` with the `zones` source. The source pages records through the read-only tool `technitium_dns_list_zones`. | `tests/test_ingest_sources.py::test_declares_ingestible_sources` validates the packaged file, resolves its tool to a client read operation and its record type to a manifest `schema_mappings` entry. | requirement | CONN-TECHNITIUM-DNS-MCP | VERIFIED | 425958bd488a tests/test_ingest_sources.py:14 |