A

Delivery structure

2 specs, 4 requirements, 1 with no code mapped
Knuckles-Team/mattermost-mcpSpec delivery
Specs (2)
  • CONN-MATTERMOST-MCP-CONNECTOR-CONTENT1
  • CONN-MATTERMOST-MCP-SDK-CENTRALIZATION3
Records not done
  • Requirementsall slices in all specs4
  • Requirements not donenot VERIFIED3
  • Specs not donewhole specs only1

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

B

Delivery states

count of total

Requirements (4)

SPECIFIED (specified)3 of 4 requirements
VERIFIED (verified)1 of 4 requirements

Specs (2)

SPECIFIED (specified)1 of 2 specs
VERIFIED (verified)1 of 2 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-MATTERMOST-MCP-CONNECTOR-CONTENTCONN-MATTERMOST-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
CONN-MATTERMOST-MCP-SDK-CENTRALIZATIONCONN-MATTERMOST-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in mattermost-mcp30/30SPECIFIEDmattermost_mcp/api/api_client_base.py implementation: file exists; coverage not verified
`requirements.md` documentation: file exists; coverage not verified
`status.json` implementation: 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/mattermost-mcp / Unassigned (2)
Knuckles-Team/mattermost-mcp / Unassigned (2)CONN-MATTERMOST-MCP-CONNECTOR-CONTENTCONN-MATTERMOST-MCP-SDK-CENTRALIZATION

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

CONN-MATTERMOST-MCP-SDK-CENTRALIZATION: 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/mattermost-mcp / Unassigned
SpecRelationshipTargetEvidence
CONN-MATTERMOST-MCP-CONNECTOR-CONTENTNo relationships declared; dependencies unknown
CONN-MATTERMOST-MCP-SDK-CENTRALIZATIONNo 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

      6 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 (6 rows)
      ID / sourceKindParentStateCommit / test evidence
      CONN-MATTERMOST-MCP-CONNECTOR-CONTENT
      CONN-MATTERMOST-MCP-CONNECTOR-CONTENT — The connector serves its packaged content      		specNoneVERIFIEDNo recorded commit/test evidence
      CONN-MATTERMOST-MCP-CONNECTOR-CONTENT-R001
      Default content
      Definition — CONN-MATTERMOST-MCP-CONNECTOR-CONTENT / CONN-MATTERMOST-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source
      **Default content.** `pyproject.toml` declares `mattermost-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-MATTERMOST-MCP-CONNECTOR-CONTENTVERIFIED68ea29159745
      tests/test_default_content_surfaces.py:15
      CONN-MATTERMOST-MCP-SDK-CENTRALIZATION
      CONN-MATTERMOST-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in mattermost-mcp      		specNoneSPECIFIEDNo recorded commit/test evidence
      CONN-MATTERMOST-MCP-SDK-CENTRALIZATION-R001
      Requests use the governed SDK client
      Definition — CONN-MATTERMOST-MCP-SDK-CENTRALIZATION / CONN-MATTERMOST-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in mattermost-mcpCanonical requirement and verification source
      **Requests use the governed SDK client.** mattermost-mcp must send every vendor request through the SDK governed HTTP client with its resolved TLS profile and SDK auth. It must not build its own session. This row follows `SDK-CENTRALIZED-CAPABILITIES-R001`, `SDK-CENTRALIZED-CAPABILITIES-R003`, `SDK-CENTRALIZED-CAPABILITIES-R008`. | A unit test shows the API client holds an httpx client and a request carries the configured credential through a mock transport
      		requirementCONN-MATTERMOST-MCP-SDK-CENTRALIZATIONSPECIFIEDtests/test_sdk_centralization.py:27
      CONN-MATTERMOST-MCP-SDK-CENTRALIZATION-R002
      SDK floor and dependency set
      Definition — CONN-MATTERMOST-MCP-SDK-CENTRALIZATION / CONN-MATTERMOST-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in mattermost-mcpCanonical requirement and verification source
      **SDK floor and dependency set.** The package must require the current agent-connector-sdk floor and must not pin requests or httpx while nothing imports them directly. Optional drivers come from SDK extras. This row follows `SDK-CENTRALIZED-CAPABILITIES-R040`, `SDK-CENTRALIZED-CAPABILITIES-R001`. | pyproject.toml shows the floor and no unused requests pin
      		requirementCONN-MATTERMOST-MCP-SDK-CENTRALIZATIONSPECIFIEDtests/test_sdk_centralization.py:58
      CONN-MATTERMOST-MCP-SDK-CENTRALIZATION-R003
      Production wiring and hot path
      Definition — CONN-MATTERMOST-MCP-SDK-CENTRALIZATION / CONN-MATTERMOST-MCP-SDK-CENTRALIZATION — Shared SDK capabilities in mattermost-mcpCanonical requirement and verification source
      **Production wiring and hot path.** `ApiClientBase.__init__` in `mattermost_mcp/api/api_client_base.py` calls `create_http_client`, and every domain client reaches it through `request`. A transient 503 is retried by the SDK policy. This row follows `SDK-CENTRALIZED-CAPABILITIES-R001`, `SDK-CENTRALIZED-CAPABILITIES-R003`, `SDK-CENTRALIZED-CAPABILITIES-R008`. | A test builds the client with a mock transport, sees a 503 then a 200, and gets one result
      		requirementCONN-MATTERMOST-MCP-SDK-CENTRALIZATIONSPECIFIEDtests/test_sdk_centralization.py:27
      tests/test_sdk_centralization.py:43
      TitleSpec delivery: mattermost-mcp
      RepositoryKnuckles-Team/mattermost-mcp
      Commita700b44b1e74
      Captured (UTC)2026-10-23T22:56:20
      Snapshotsnapshot.json (v1)
      Sourcespecs/*/status.json
      Sheet1 of 1