- CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT1
- CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS1
- CONN-OBJECTSTORE-MCP10
- Requirementsall slices in all specs12
- Requirements not donenot VERIFIED3
- Specs not donewhole specs only3
Each spec shows its requirement count. Panel J lists every record.
Requirements (12)
Specs (3)
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-OBJECTSTORE-MCP-CONNECTOR-CONTENTCONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | 1 | 1/1 | 0 | LANDED | objectstore_mcp/__init__.py:13 implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified ../../objectstore_mcp/__init__.py implementation: file exists; coverage not verified |
| CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONSCONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS — Operations the data-platform vocabulary needs | 1 | 0/1 | 0 | SPECIFIED | requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified ../../objectstore_mcp/__init__.py implementation: file exists; coverage not verified objectstore_mcp/mcp/mcp_objectstore.py implementation: file exists; coverage not verified |
| CONN-OBJECTSTORE-MCPCONN-OBJECTSTORE-MCP — Object storage connector backends | 10 | 10/10 | 9 | LANDED | objectstore_mcp/api/__init__.py implementation: file exists; coverage not verified objectstore_mcp/ontology/objectstore.ttl implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified tests/test_objectstore_mcp_validation.py test: file exists; coverage not verified tests/test_safety.py test: file exists; coverage not verified tests/test_sdk_backends.py test: file exists; coverage not verified tests/test_surface_ontology.py test: file exists; coverage not verified ../../objectstore_mcp/auth.py implementation: file exists; coverage not verified ../../objectstore_mcp/config.py implementation: file exists; coverage not verified ../../objectstore_mcp/guard.py implementation: file exists; coverage not verified ../../objectstore_mcp/mcp/mcp_objectstore.py implementation: file exists; coverage not verified contracts/storage-backends.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/objectstore-mcp / objectstore-mcp connector (3)
CONN-OBJECTSTORE-MCP: no plan diagram declared.
CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT: no plan diagram declared.
CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS: 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/objectstore-mcp / objectstore-mcp connector
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-OBJECTSTORE-MCP | No relationships declared; dependencies unknown | ||
| CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT | No relationships declared; dependencies unknown | ||
| CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS | 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 (15 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT — The connector serves its packaged content | spec | None | LANDED | No recorded commit/test evidence |
| CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT-R001 Default content Definition — CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT / CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Default content.** `pyproject.toml` declares `objectstore-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: `objectstore-mcp` in `pyproject.toml` runs `scion_sdk.cli:serve`, which builds the server from the `scion_sdk.connector` entry point `objectstore_mcp:connector` (`objectstore_mcp/__init__.py:13`); the SDK `Connector` then lists the packaged skills, ontology and prompts. Shape: `pyproject.toml` entry point `objectstore-mcp` plus the `connector = Connector(.)` object in `objectstore_mcp/__init__.py`; the packaged `skills/`, `ontology/` and `prompts/` directories of `objectstore_mcp` 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`. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt. | requirement | CONN-OBJECTSTORE-MCP-CONNECTOR-CONTENT | LANDED | 87e282b54a27 dc8f44e13341 |
| CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS — Operations the data-platform vocabulary needs | spec | None | SPECIFIED | No recorded commit/test evidence |
| CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS-R001 Last-access operation Definition — CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS / CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS — Operations the data-platform vocabulary needsCanonical requirement and verification source**Last-access operation.** `objectstore_head_object` and `objectstore_list_objects` report a last-access time, or a typed `unsupported` result for backends without one. Touches `objectstore_mcp/mcp/mcp_objectstore.py`. Moved from `MEDULLA-DATAPLAT-VOCAB-R009.1` (medulla). Caller chain: arbora `fleet.call` reaches the SDK-generated `objectstore_head_object` tool, which calls `S3Backend.head_object` in the SDK storage backends. Shape: a `last_accessed` field on `head` and `list` results from the backend, or a typed `unsupported` result; extends the `LastModified` mapping of the SDK S3 backend. Proving test (planned): `tests/test_last_access_operation.py::test_head_and_list_carry_last_accessed_or_unsupported`. | a `head`/`list` result carries `last_accessed` or the operation returns typed `unsupported`. | requirement | CONN-OBJECTSTORE-MCP-DATA-PLATFORM-OPERATIONS | SPECIFIED | No recorded commit/test evidence |
| CONN-OBJECTSTORE-MCP CONN-OBJECTSTORE-MCP — Object storage connector backends | spec | None | LANDED | No recorded commit/test evidence |
| CONN-OBJECTSTORE-MCP-R001 Serve every store through the SDK backends Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Serve every store through the SDK backends.** The connector deletes `objectstore_mcp/api/api_client_base.py` and the four `api_client_*` backend modules. `objectstore_mcp/auth.py` builds each backend with `create_backend` from `scion_sdk.storage` (`SCION-CENTRALIZED-CAPABILITIES-R042.6`). `objectstore_mcp/config.py` parses `OBJECTSTORE_STORES` with `parse_stores` and keeps the implicit `local` filesystem store. It also keeps the tool-layer `Limits`. The tool layer catches `StorageError` and maps its `code` to the tool error. Store credentials move to the store `credentials` map as secret references. The ambient provider profile and the `profile` field are removed in the same release. Caller chain: MCP `tools/call` → the tool function in `objectstore_mcp/mcp/mcp_objectstore.py` → `get_backend` (objectstore_mcp/auth.py:78) → `create_backend` in the SDK. Shape: `objectstore_mcp/api/__init__.py` re-exports the SDK names the tool layer uses; no backend class stays in the package. Depends on: `SCION-CENTRALIZED-CAPABILITIES-R042`. | `tests/test_sdk_backends.py::test_tools_route_through_sdk_backends_and_no_local_copy` (planned in `test-spec.md`). A tool call on a filesystem store returns the object. `objectstore_mcp/api/` holds no class with a `backend_type`. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 5cca1bbf1eec tests/test_sdk_backends.py:17 |
| CONN-OBJECTSTORE-MCP-R002 Take the provider libraries from the SDK extras Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Take the provider libraries from the SDK extras.** `pyproject.toml` pins the SDK release that carries the storage backends. The connector extras `s3`, `gcs` and `azure` name the SDK extras `storage-s3`, `storage-gcs` and `storage-azure`. The connector pins no provider library itself. Caller chain: `pip install objectstore-mcp[s3]` → the SDK extra → the provider library imported by `S3Backend`. Shape: edit `[project.dependencies]` and `[project.optional-dependencies]`; relock `uv.lock`. Depends on: `SCION-CENTRALIZED-CAPABILITIES-R042`. | `tests/test_sdk_backends.py::test_extras_name_the_sdk_storage_extras` (planned in `test-spec.md`). Each connector extra names exactly one SDK storage extra and no provider library. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 1b16ad56f9bf 5cca1bbf1eec tests/test_sdk_backends.py:28 tests/test_sdk_backends.py:84 |
| CONN-OBJECTSTORE-MCP-R003 Accept WebDAV stores Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Accept WebDAV stores.** A store with backend `webdav` builds the SDK `WebDavBackend` (`SCION-CENTRALIZED-CAPABILITIES-R042.5`). Its `endpoint` is the collection root URL. Its `credentials` map holds `username` and `password` references. The object tools then work on that file share. Presign and metadata tools return the SDK refusal `STORAGE_UNSUPPORTED`. Caller chain: `get_backend` (objectstore_mcp/auth.py:78) → `create_backend` → `WebDavBackend`. Shape: no connector code beyond configuration; the test pins the routing. Depends on: `CONN-OBJECTSTORE-MCP-R001`, `SCION-CENTRALIZED-CAPABILITIES-R042.5`. | `tests/test_sdk_backends.py::test_webdav_store_routes_through_sdk` (planned in `test-spec.md`). A `webdav` store builds a `WebDavBackend`. A presign call returns `STORAGE_UNSUPPORTED`. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 5cca1bbf1eec tests/test_sdk_backends.py:44 |
| CONN-OBJECTSTORE-MCP-R004 Name the SDK by its current name in every document Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Name the SDK by its current name in every document.** `AGENTS.md`, `README.md` and `docs/` link the SDK by its current package name and site. The changelog keeps its released entries unchanged. Caller chain: none; the documents ship in the repository and the site. Shape: replace the retired name and site link in the three places. | `tests/test_sdk_backends.py::test_no_retired_sdk_name_in_package_or_docs` (planned in `test-spec.md`). The package, `AGENTS.md`, `README.md` and `docs/` hold 0 matches for the retired name. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 5cca1bbf1eec tests/test_sdk_backends.py:71 |
| CONN-OBJECTSTORE-MCP-R002.1 Ship every provider library in the served image Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Ship every provider library in the served image.** `[tool.pipelines.container] install_extras` installs the `s3`, `gcs` and `azure` extras into the `mcp` image target, so a configured `s3` store does not refuse with `STORAGE_DEPENDENCY_MISSING` in production. The `all` extra names the three extras without a version floor on itself. Caller chain: the release image build → `pip install objectstore-mcp[s3,gcs,azure]` → `S3Backend` imports boto3. Shape: edit `pyproject.toml` only. Depends on: `CONN-OBJECTSTORE-MCP-R002`. | `tests/test_sdk_backends.py::test_served_image_installs_every_provider_extra`. The `mcp` target installs `s3`, `gcs` and `azure`. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 1b16ad56f9bf tests/test_sdk_backends.py:84 |
| CONN-OBJECTSTORE-MCP-R005 One typed tool per operation, and refusals that keep their cause Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**One typed tool per operation, and refusals that keep their cause.** The connector serves no `action`-routed tool. The SDK generates one tool per `ObjectStoreBackend` method; `objectstore_mcp/mcp/mcp_objectstore.py` adds one typed tool per extra operation: `objectstore_list_stores`, `objectstore_move_object`, `objectstore_delete_objects_by_prefix`, `objectstore_upload_file`, `objectstore_download_file`, `objectstore_upload_directory`, `objectstore_download_prefix`, `objectstore_ingest_buckets` and `objectstore_ingest_objects`, each with an optional `store`. `get_client` (objectstore_mcp/auth.py) keeps the SDK refusal code and message (`AUTHENTICATION ERROR: <code>: <message>`) and names an entitlement denial, instead of the bare exception type. Caller chain: MCP `tools/call` → the tool → `get_backend` → `create_backend`. Shape: the action-routed `objects`, `buckets`, `transfer` and `objectstore_ingest` tools and `objectstore_mcp/objectstore_input_models.py` are removed in the same release. Depends on: `CONN-OBJECTSTORE-MCP-R001`. | `tests/test_objectstore_mcp_validation.py::test_tool_inventory_is_typed_with_no_action_routing`, `tests/test_objectstore_mcp_validation.py::test_refusal_keeps_the_storage_cause`. No served tool has an `action` or `params_json` parameter or the `split-action` tag; an egress refusal reads `STORAGE_EGRESS_REFUSED`. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 1b16ad56f9bf tests/test_objectstore_mcp_validation.py:19 tests/test_objectstore_mcp_validation.py:248 |
| CONN-OBJECTSTORE-MCP-R006 The safety governor wraps every tool's backend Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**The safety governor wraps every tool's backend.** `objectstore_mcp/guard.py` `GuardedBackend` wraps the backend `get_backend` returns, so the SDK-generated tools and the typed tools both enforce the get, put and list caps, refuse wildcard single-object deletes, and honour `OBJECTSTORE_ALLOW_DELETE` and `OBJECTSTORE_ALLOW_BUCKET_DELETE`. Prefix deletes run as a dry run unless `dry_run=false` and are count-capped. Caller chain: tool → `get_backend` (objectstore_mcp/auth.py) → `GuardedBackend` → SDK backend. Shape: new module `objectstore_mcp/guard.py`; the backends stay pure adapters. Depends on: `CONN-OBJECTSTORE-MCP-R005`. | `tests/test_safety.py` (every test). A put over the cap, a bucket delete with the flag off and a wildcard delete each refuse; a prefix delete without `dry_run=false` deletes nothing. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 1b16ad56f9bf tests/test_safety.py:106 tests/test_safety.py:113 tests/test_safety.py:127 tests/test_safety.py:134 tests/test_safety.py:145 |
| CONN-OBJECTSTORE-MCP-R007 Manage S3 bucket lifecycle, versioning and object tags Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Manage S3 bucket lifecycle, versioning and object tags.** Typed tools `objectstore_get_bucket_lifecycle`, `objectstore_put_bucket_lifecycle` (rules with `id`, `prefix`, `enabled`, `expiration_days`, `noncurrent_expiration_days`, `abort_incomplete_multipart_days`, `transition_days`, `storage_class`), `objectstore_delete_bucket_lifecycle`, `objectstore_get_bucket_versioning`, `objectstore_put_bucket_versioning`, `objectstore_get_object_tags`, `objectstore_put_object_tags` and `objectstore_delete_object_tags` call the S3 client of an `s3` store. Any other backend refuses with `STORAGE_UNSUPPORTED`. An absent lifecycle or tag set reads as empty. A rule with no action refuses. Caller chain: tool → `_s3_client` (objectstore_mcp/mcp/mcp_objectstore.py) → `S3Backend.client`. Shape: tools only; no backend change. Depends on: `CONN-OBJECTSTORE-MCP-R005`. | `tests/test_objectstore_mcp_validation.py::test_s3_lifecycle_versioning_and_tags`, `tests/test_objectstore_mcp_validation.py::test_s3_management_refuses_on_filesystem_store`. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 1b16ad56f9bf tests/test_objectstore_mcp_validation.py:158 tests/test_objectstore_mcp_validation.py:206 |
| CONN-OBJECTSTORE-MCP-R008 Package the complete surface Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Package the complete surface.** The package serves, beside the tools: the skills `objectstore-object-operations`, `objectstore-bucket-administration`, `objectstore-data-transfer` and `objectstore-mcp-operations` rewritten for the typed tools, and the business skill `objectstore-business-asset-store` (key layout, stage tags, retention and the presigned-URL handoff of business media); the business-role prompt `prompts/objectstore_asset_librarian.json`; and an ontology whose classes roll up to core by `rdfs:subClassOf` (`:ObjectStore` and `:Bucket` under `:StorageContainer`, `:Object` under `:File`), never `owl:imports`, and that records each served tool as a `:Tool`, each skill's tools, the prompt agent's prompt, skills and tools, the tool-use contracts as `:Task` with ordered `:TaskStep`s, and the data location of the `objectstore-objects` source. Caller chain: fastmcp content serving of `skills/`, `prompts/` and `ontology/`. Shape: content files plus `connector_sources.py` mappings to the ontology classes. Depends on: `CONN-OBJECTSTORE-MCP-R005`. | `tests/test_surface_ontology.py` (every test). The ontology's tools equal the served tools; every tool a skill, the prompt or a contract names is served. | requirement | CONN-OBJECTSTORE-MCP | VERIFIED | 1b16ad56f9bf tests/test_surface_ontology.py:19 tests/test_surface_ontology.py:25 tests/test_surface_ontology.py:45 |
| CONN-OBJECTSTORE-MCP-R009 Adopt scion-sdk 0.10.0 import paths Definition — CONN-OBJECTSTORE-MCP / CONN-OBJECTSTORE-MCP — Object storage connector backendsCanonical requirement and verification source**Adopt scion-sdk 0.10.0 import paths.** objectstore-mcp must import only paths that exist in `scion-sdk` 0.10.0 and must raise its floor to that release. The release removes the pre-layer paths without an alias (`SCION-CENTRALIZED-CAPABILITIES-R046`). Stage: dependency and import adoption. Edits, by file: `tests/conftest.py`: `scion_sdk._connector_serve` to `scion_sdk.connector (import `build_server` from the package)`. Raise the `pyproject.toml` requirement `scion-sdk[mcp]>=0.9.0` to `scion-sdk>=0.10.0,<0.11.0` with the same extras and regenerate `uv.lock`. A client built by the old factory keeps its options argument; `build_http_client(options, async_=True)` returns the async client. No wrapper, alias or fallback import stays. Caller chain: the connector entry point `objectstore_mcp` -> its modules above -> the public `scion_sdk` modules. Shape: import edits in the files named, one `pyproject.toml` edit and one lock edit; the new test reuses `ast` from the standard library. Depends on: SCION-CENTRALIZED-CAPABILITIES-R046. | Test: `tests/test_scion_sdk_0_10_imports.py::test_every_scion_sdk_import_resolves_on_the_pinned_release` (L2) parses every Python file of `objectstore_mcp` and `tests` and asserts each imported `scion_sdk` module resolves with `importlib.util.find_spec`. | requirement | CONN-OBJECTSTORE-MCP | LANDED | 44fc2357ea67 |