A

Delivery structure

1 specs, 4 requirements, 0 with no code mapped
Knuckles-Team/portainer-agentSpec delivery
Specs (1)
  • CONN-PORTAINER-AGENT-CONNECTOR-CONTENT4
Records not done
  • Requirementsall slices in all specs4
  • Requirements not donenot VERIFIED4
  • 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)1 of 4 requirements
LANDED (landed)3 of 4 requirements

Specs (1)

SPECIFIED (specified)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-PORTAINER-AGENT-CONNECTOR-CONTENTCONN-PORTAINER-AGENT-CONNECTOR-CONTENT — The connector serves its packaged content43/40SPECIFIEDportainer_agent/__init__.py:94 implementation: file exists; coverage not verified
portainer_agent/mcp_server.py implementation: file exists; coverage not verified
requirements.md documentation: file exists; coverage not verified
spec.md documentation: file exists; coverage not verified
../../portainer_agent/__init__.py 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/portainer-agent / portainer-agent connector (1)
Knuckles-Team/portainer-agent / portainer-agent connector (1)CONN-PORTAINER-AGENT-CONNECTOR-CONTENT

CONN-PORTAINER-AGENT-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/portainer-agent / portainer-agent connector
SpecRelationshipTargetEvidence
CONN-PORTAINER-AGENT-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

      5 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 (5 rows)
      ID / sourceKindParentStateCommit / test evidence
      CONN-PORTAINER-AGENT-CONNECTOR-CONTENT
      CONN-PORTAINER-AGENT-CONNECTOR-CONTENT — The connector serves its packaged content
      specNoneSPECIFIEDNo recorded commit/test evidence
      CONN-PORTAINER-AGENT-CONNECTOR-CONTENT-R001
      Default content
      Definition — CONN-PORTAINER-AGENT-CONNECTOR-CONTENT / CONN-PORTAINER-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source
      **Default content.** `pyproject.toml` declares `portainer-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. Caller chain: `portainer-mcp` in `pyproject.toml` runs `scion_sdk.cli:serve`, which builds the server from the `scion_sdk.connector` entry point `portainer_agent:connector` (`portainer_agent/__init__.py:94`); the SDK `Connector` then lists the packaged skills, ontology and prompts. Shape: `pyproject.toml` entry point `portainer-mcp` plus the `connector = Connector(.)` object in `portainer_agent/__init__.py`; the packaged `skills/`, `ontology/` and `prompts/` directories of `portainer_agent` are reused as is, with no connector-local registration code. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt.
      requirementCONN-PORTAINER-AGENT-CONNECTOR-CONTENTLANDED069df7a3125f
      63de16a8e809
      CONN-PORTAINER-AGENT-CONNECTOR-CONTENT-R002
      Declare access contracts for the competency reads of portainer-agent
      Definition — CONN-PORTAINER-AGENT-CONNECTOR-CONTENT / CONN-PORTAINER-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source
      **Declare access contracts for the competency reads of portainer-agent.** Subsystem: connector `portainer-agent`. Caller: the connector's existing read tool, called by arbora through `fleet.call`. Declare in `portainer_agent/ontology/access_contracts.ttl` one `ac:AccessContract` per entity. Entities: entity `stack` (class stack, key `id`, columns name, gitUrl, endpointId). Each row sets `ac:classIri`, `ac:sourceId`, `ac:entity`, `ac:keyField`, `ac:accessKind` `mcp_tool`, `ac:operation` (the existing tool name) and `ac:pagination`. Column names equal the ontology property local names. Follow the `ac:AccessContract` vocabulary of the SDK. Save one recorded response per entity in `tests/recordings/<entity>.json`. Medulla copies these into its competency fixtures. The consumer is the medulla table row MEDULLA-CQ-CONN-R086. Caller chain: arbora `fleet.call` reaches the existing read tool of `portainer_agent/mcp_server.py`, whose result is validated against the `ac:AccessContract` rows declared in `portainer_agent/ontology/access_contracts.ttl`. Shape: `portainer_agent/ontology/access_contracts.ttl` with one `ac:AccessContract` per entity named in the row; reuses the existing read tool and the SDK ontology certification, no new tool. Proving test (planned): `tests/test_access_contracts.py::test_competency_contracts_certified`. Proving test (planned): `tests/test_access_contracts.py::test_competency_contracts_certified`. Proving test (planned): `tests/test_access_contracts.py::test_competency_contracts_certified`. Proving test (planned): `tests/test_access_contracts.py::test_competency_contracts_certified`. | Test: `tests/test_access_contracts.py::test_competency_contracts_certified` (L2) runs the connector ontology certification and validates each recording against its contract.
      requirementCONN-PORTAINER-AGENT-CONNECTOR-CONTENTSPECIFIEDNo recorded commit/test evidence
      CONN-PORTAINER-AGENT-CONNECTOR-CONTENT-R003
      Served dispatch targets exist
      Definition — CONN-PORTAINER-AGENT-CONNECTOR-CONTENT / CONN-PORTAINER-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source
      **Served dispatch targets exist.** Every client method the served action dispatch references exists on the client, so a missing method cannot make every action of a tool raise. Proving test: `tests/test_served_dispatch_targets_exist.py`. | Docker system usage, edge stack and job creation, and custom template creation resolve to client methods.
      requirementCONN-PORTAINER-AGENT-CONNECTOR-CONTENTLANDED6297a2498c73
      CONN-PORTAINER-AGENT-CONNECTOR-CONTENT-R004
      Kubernetes RBAC and Helm chart reads call served routes
      Definition — CONN-PORTAINER-AGENT-CONNECTOR-CONTENT / CONN-PORTAINER-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source
      **Kubernetes RBAC and Helm chart reads call served routes.** The Kubernetes RBAC listing tools call the routes Portainer serves (`cluster_role_bindings`, `cluster_roles`, `role_bindings`, `service_accounts`), and the Helm chart listing tool takes the chart repository URL and sends it as the required `repo` query parameter. Proving test: `tests/test_kubernetes_rbac_and_helm_routes.py`. | The RBAC listings and the Helm chart listing return data from a Kubernetes environment instead of 404 or 400.
      requirementCONN-PORTAINER-AGENT-CONNECTOR-CONTENTLANDED75b69d815c7b
      TitleSpec delivery: portainer-agent
      RepositoryKnuckles-Team/portainer-agent
      Commit63de16a8e809
      Captured (UTC)2026-11-06T18:39:57
      Snapshotsnapshot.json (v1)
      Sourcespecs/*/status.json
      Sheet1 of 1