A

Delivery structure

2 specs, 2 requirements, 1 with no code mapped
Knuckles-Team/firefly-iii-mcpSpec delivery
Specs (2)
  • CONN-FIREFLY-III-MCP-CONNECTOR-CONTENT1
  • CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION1
Records not done
  • Requirementsall slices in all specs2
  • Requirements not donenot VERIFIED2
  • Specs not donewhole specs only2

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

B

Delivery states

count of total

Requirements (2)

SPECIFIED (specified)1 of 2 requirements
LANDED (landed)1 of 2 requirements

Specs (2)

SPECIFIED (specified)1 of 2 specs
LANDED (landed)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-FIREFLY-III-MCP-CONNECTOR-CONTENTCONN-FIREFLY-III-MCP-CONNECTOR-CONTENT — The connector serves its packaged content11/10LANDEDspec.md documentation: file exists; coverage not verified
requirements.md documentation: file exists; coverage not verified
CONN-FIREFLY-III-MCP-SDK-CENTRALIZATIONCONN-FIREFLY-III-MCP-SDK-CENTRALIZATION — SDK centralization10/10SPECIFIEDspec.md documentation: file exists; coverage not verified
Connector SDK documentation: external declaration; not verified
../../firefly_iii_mcp/api/api_client_base.py implementation: file exists; coverage not verified
../../tests/test_sdk_centralization.py test: file exists; coverage not verified
plan.md documentation: file exists; coverage not verified
requirements.md documentation: file exists; coverage not verified
test-spec.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/firefly-iii-mcp / Connector integration (1)
Knuckles-Team/firefly-iii-mcp / Connector integration (1)CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION

CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION: no plan diagram declared.

Knuckles-Team/firefly-iii-mcp / Unassigned (1)
Knuckles-Team/firefly-iii-mcp / Unassigned (1)CONN-FIREFLY-III-MCP-CONNECTOR-CONTENT

CONN-FIREFLY-III-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/firefly-iii-mcp / Connector integration
SpecRelationshipTargetEvidence
CONN-FIREFLY-III-MCP-SDK-CENTRALIZATIONreferencesConnector SDKKnuckles-Team/scion-sdk: external declaration; not verified; source: specs/sdk-centralization/spec.md
Knuckles-Team/firefly-iii-mcp / Unassigned
SpecRelationshipTargetEvidence
CONN-FIREFLY-III-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

      4 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 (4 rows)
      ID / sourceKindParentStateCommit / test evidence
      CONN-FIREFLY-III-MCP-CONNECTOR-CONTENT
      CONN-FIREFLY-III-MCP-CONNECTOR-CONTENT — The connector serves its packaged content
      specNoneLANDEDNo recorded commit/test evidence
      CONN-FIREFLY-III-MCP-CONNECTOR-CONTENT-R001
      Default content
      Definition — CONN-FIREFLY-III-MCP-CONNECTOR-CONTENT / CONN-FIREFLY-III-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source
      **Default content.** `pyproject.toml` declares `firefly-iii-mcp` as the single `scion_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-FIREFLY-III-MCP-CONNECTOR-CONTENTLANDED364dd7587f73
      CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION
      CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION — SDK centralization
      specNoneSPECIFIEDNo recorded commit/test evidence
      CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION-R001
      Governed HTTP
      Definition — CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION / CONN-FIREFLY-III-MCP-SDK-CENTRALIZATION — SDK centralizationCanonical requirement and verification source
      **Governed HTTP.** The connector must reach Firefly III only through the SDK governed HTTP client in `firefly_iii_mcp/api/api_client_base.py`. It must not import `requests`. | `tests/test_sdk_centralization.py::test_api_client_uses_sdk_http_client` must observe an SDK client and no `requests` import.
      requirementCONN-FIREFLY-III-MCP-SDK-CENTRALIZATIONSPECIFIEDNo recorded commit/test evidence
      TitleSpec delivery: firefly-iii-mcp
      RepositoryKnuckles-Team/firefly-iii-mcp
      Commit88010a2141ca
      Captured (UTC)2026-10-31T04:38:18
      Snapshotsnapshot.json (v1)
      Sourcespecs/*/status.json
      Sheet1 of 1