- CONN-CISO-ASSISTANT-API4
- CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT2
- Requirementsall slices in all specs6
- Requirements not donenot VERIFIED2
- Specs not donewhole specs only2
Each spec shows its requirement count. Panel J lists every record.
Requirements (6)
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-CISO-ASSISTANT-APICONN-CISO-ASSISTANT-API — Credential reference resolution | 4 | 3/4 | 3 | SPECIFIED | spec.md documentation: file exists; coverage not verified ../../ciso_assistant_api/api/api_client_base.py implementation: file exists; coverage not verified ../../ciso_assistant_api/auth.py implementation: file exists; coverage not verified ../../pyproject.toml implementation: file exists; coverage not verified ../../tests/test_auth.py test: file exists; coverage not verified ../../tests/test_credential_refs.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 |
| CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENTCONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT — The connector serves its packaged content | 2 | 1/2 | 1 | SPECIFIED | ciso_assistant_api/mcp_server.py implementation: file exists; coverage not verified spec.md documentation: 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.
Packages group specs by repository and declared component. Unassigned means no component was declared. Code links do not prove coverage. Mermaid source.
Knuckles-Team/ciso-assistant-api / Connector integration (1)
CONN-CISO-ASSISTANT-API: no plan diagram declared.
Knuckles-Team/ciso-assistant-api / Unassigned (1)
CONN-CISO-ASSISTANT-API-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/ciso-assistant-api / Connector integration
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-CISO-ASSISTANT-API | No relationships declared; dependencies unknown | ||
Knuckles-Team/ciso-assistant-api / Unassigned
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-CISO-ASSISTANT-API-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 (8 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| CONN-CISO-ASSISTANT-API CONN-CISO-ASSISTANT-API — Credential reference resolution | spec | None | SPECIFIED | No recorded commit/test evidence |
| CONN-CISO-ASSISTANT-API-R001 SDK floor Definition — CONN-CISO-ASSISTANT-API / CONN-CISO-ASSISTANT-API — Credential reference resolutionCanonical requirement and verification source**SDK floor.** `pyproject.toml` must require `scion-sdk[mcp]>=0.5.6,<1.0.0`, the compatible renamed SDK release preserving the credential behavior introduced in scion-sdk 0.3.10, where `default_credential_resolver()` serves `env://` when `OPENBAO_TOKEN_REF` is unset. Caller chain: the `ciso-assistant-mcp` console script (`ciso_assistant_api.mcp_server:mcp_server`, line 79) -> `get_mcp_instance` (line 72) -> SDK `build_server("ciso_assistant_api")` -> `get_client` (`ciso_assistant_api/auth.py` line 53), whose secret resolution depends on the SDK floor declared in `pyproject.toml`. Shape: the floor is the `scion-sdk[mcp]` requirement in `pyproject.toml` dependencies and the `mcp` and `all` extras; `tests/test_credential_refs.py::test_sdk_floor_is_declared` parses the requirement with `packaging` and checks its range. | `tests/test_credential_refs.py::test_sdk_floor_is_declared` must pass. | requirement | CONN-CISO-ASSISTANT-API | VERIFIED | 262cb1a5cdaf tests/test_credential_refs.py:11 |
| CONN-CISO-ASSISTANT-API-R002 Wiring Definition — CONN-CISO-ASSISTANT-API / CONN-CISO-ASSISTANT-API — Credential reference resolutionCanonical requirement and verification source**Wiring.** `get_client` in `ciso_assistant_api/auth.py` must resolve `CISO_ASSISTANT_USERNAME_REF` and `CISO_ASSISTANT_PASSWORD_REF` through `resolve_secret_reference` with `OPENBAO_ADDR` set and no `OPENBAO_TOKEN_REF`. Caller chain: `ciso_assistant_api/mcp_server.py::register_server_surface` (line 32) passes `get_client` to `register_tool_surface` -> `get_client` (`ciso_assistant_api/auth.py` line 53) -> `_resolve_optional_secret` (line 120) -> `scion_sdk.credentials.resolution.resolve_secret_reference`. Shape: `get_client` reads `CISO_ASSISTANT_USERNAME_REF` and `CISO_ASSISTANT_PASSWORD_REF` through `scion_sdk.config.setting` and `_resolve_optional_secret`; the test sets `env://` references with `OPENBAO_ADDR` and no `OPENBAO_TOKEN_REF` and builds the client. | `tests/test_credential_refs.py::test_env_refs_resolve_with_openbao_addr_and_no_token_ref` must build a client through `get_client`. | requirement | CONN-CISO-ASSISTANT-API | VERIFIED | 9f84a516227f tests/test_credential_refs.py:20 |
| CONN-CISO-ASSISTANT-API-R003 Headless login Definition — CONN-CISO-ASSISTANT-API / CONN-CISO-ASSISTANT-API — Credential reference resolutionCanonical requirement and verification source**Headless login.** `_ensure_token` in `ciso_assistant_api/api/api_client_base.py` must use a configured token without logging in; otherwise it must `POST /api/_allauth/app/v1/auth/login` with JSON `email` (or `username` when the identity has no `@`) and `password`, and use `meta.access_token` from the response as the API token. It must not call `/api/iam/login/`. Caller chain: any API tool call -> `Api` client method in `ciso_assistant_api/api/` -> `_auth_headers` (`ciso_assistant_api/api/api_client_base.py` line 152) -> `_ensure_token` (line 116), which posts the headless login when no token is configured. Shape: `_ensure_token` caches the token under `_token_lock` and posts JSON `email` or `username` plus `password` to `/api/_allauth/app/v1/auth/login` with the session in `api_client_base.py`; `tests/test_auth.py` covers the login and the configured-token paths. | `tests/test_auth.py::test_headless_login_returns_access_token` and `tests/test_auth.py::test_configured_token_skips_login` must pass. | requirement | CONN-CISO-ASSISTANT-API | SPECIFIED | No recorded commit/test evidence |
| CONN-CISO-ASSISTANT-API-R004 Fleet name Definition — CONN-CISO-ASSISTANT-API / CONN-CISO-ASSISTANT-API — Credential reference resolutionCanonical requirement and verification source**Fleet name.** `pyproject.toml` declares `ciso-assistant-mcp` as the single `scion_sdk.connector` entry point. The content pack, the manifest `connector`, the fingerprints and the ingest binding all carry `ciso-assistant-mcp`. Proving test: `tests/test_fleet_name.py::test_connector_name_is_the_fleet_name`. Caller chain: the `ciso-assistant-mcp = ciso_assistant_api:connector` entry point in `pyproject.toml` -> `ciso_assistant_api/__init__.py::connector` (line 76) -> `IngestBinding` and `ConnectorContent` calls that carry the connector name. Shape: the name is a literal in `pyproject.toml` and the package calls; `tests/test_fleet_name.py` walks the package by AST and compares every `connector` keyword with the fleet name. | Every connector name in the package is `ciso-assistant-mcp`. | requirement | CONN-CISO-ASSISTANT-API | VERIFIED | 60bd1be05869 9f84a516227f e8d176cf25c8 tests/test_fleet_name.py:34 |
| CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT — The connector serves its packaged content | spec | None | SPECIFIED | No recorded commit/test evidence |
| CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT-R001 Default content Definition — CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT / CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Default content.** `pyproject.toml` declares `ciso-assistant-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`. Caller chain: the `ciso-assistant-mcp = ciso_assistant_api:connector` entry point in `pyproject.toml` -> `ciso_assistant_api/__init__.py::connector` (line 76) -> SDK `build_server("ciso_assistant_api")` called by `ciso_assistant_api/mcp_server.py::get_mcp_instance` (line 72), serving the packaged skills, prompts and ontology. Shape: content comes from the packaged `ciso_assistant_api/skills/`, `prompts/` and `ontology/` directories through the SDK build, with no `content=` argument in the connector; the test lists resources and prompts through `fastmcp.Client`. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt. Test: `tests/test_default_content_surfaces.py::test_default_content_surfaces`. | requirement | CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT | VERIFIED | 262cb1a5cdaf 4317988a9190 tests/test_default_content_surfaces.py:15 |
| CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT-R002 Declare access contracts for the competency reads of ciso-assistant-api Definition — CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT / CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Declare access contracts for the competency reads of ciso-assistant-api.** Subsystem: connector `ciso-assistant-api`. Caller: the connector's existing read tool, called by arbora through `fleet.call`. Declare in `ciso_assistant_api/ontology/access_contracts.ttl` one `ac:AccessContract` per entity. Entities: entity `applied_control` (class control, key `id`, columns status, riskScenarioId); entity `risk_scenario` (class RiskScenario, key `id`, columns serviceRef, name). 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 access contracts file of the container-manager-mcp connector (`access_contracts.ttl` under its `ontology` directory). 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` -> condensed domain tools from `register_server_surface` (`ciso_assistant_api/mcp_server.py` line 32, `TOOL_REGISTRY`) with actions `api_applied_controls_list` and `api_risk_scenarios_list` -> `ciso_assistant_api/api/` client; the new the new `ciso_assistant_api` access contracts file does not exist yet. Shape: add `ciso_assistant_api/ontology/access_contracts.ttl` next to `ciso.ttl` following the access contracts file of the container-manager-mcp connector (`access_contracts.ttl` under its `ontology` directory); class `RiskScenario` exists in `ciso.ttl` but `control` and the columns must be checked against it; add `tests/recordings/<entity>.json` and `risk_scenario.json`, certified through `ciso_assistant_api/ontology/certification.json`. | Test (planned): `tests/test_access_contracts.py::test_competency_contracts_certified` (L2) runs the connector ontology certification and validates each recording against its contract. | requirement | CONN-CISO-ASSISTANT-API-CONNECTOR-CONTENT | SPECIFIED | No recorded commit/test evidence |