State-hub connect and initial workplans

This commit is contained in:
2026-05-03 20:43:56 +02:00
parent ebb241dab6
commit f25bd2cf84
14 changed files with 657 additions and 2 deletions

View File

@@ -0,0 +1,88 @@
---
id: IB-WP-0001
type: workplan
title: "State Hub And Repo Bootstrap"
domain: markitect
repo: infospace-bench
status: active
owner: markitect
topic_slug: markitect
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_slug: "repo-integration-infospace-bench"
state_hub_workstream_id: "35666029-168e-4d8c-b6ce-24cb5a290156"
---
# IB-WP-0001 — State Hub And Repo Bootstrap
## Goal
Establish `infospace-bench` as a registered, navigable State Hub project with
clear scope, agent rules, and initial planning artifacts.
## Context
The repo was registered with State Hub under the `markitect` domain. The
registration created an onboarding workstream and a temporary
`CLAUDE.custodian.md` suggestion file. The suggestion referenced deprecated
template behavior, so this repo provides its own minimal integration files.
## Tasks
### T01 — Register repo in State Hub
```task
id: IB-WP-0001-T01
status: done
priority: high
state_hub_task_id: "7ef38fac-7db0-4368-bab3-4126bf4c0338"
```
- Registered repo slug `infospace-bench`
- Domain: `markitect`
- Topic ID: `5571d954-0d30-4950-980d-7bcaaad8e3e2`
- Onboarding workstream: `repo-integration-infospace-bench`
### T02 — Add agent orientation files
```task
id: IB-WP-0001-T02
status: done
priority: high
state_hub_task_id: "54dec019-76a9-4397-9cda-ae9b6cd56926"
```
- Add `SCOPE.md`
- Add `CLAUDE.md`
- Add `.claude/rules/` integration notes
### T03 — Capture migration assessment
```task
id: IB-WP-0001-T03
status: done
priority: high
state_hub_task_id: "110422cc-85cd-4668-8e99-1fe820357148"
```
- Compare `markitect-main` against `infospace-bench` PRD/FRS
- Document migrate/reimplement/defer boundaries
### T04 — Replace temporary custodian suggestion
```task
id: IB-WP-0001-T04
status: done
priority: medium
state_hub_task_id: "d37306b2-29a8-4439-aa89-754db603dbc5"
```
- Delete `CLAUDE.custodian.md` after integration is complete
- Verify `git status --short`
## Acceptance
- State Hub registration exists
- Repo contains orientation and workplan artifacts
- Migration scope is documented
- Temporary registration suggestion is removed

View File

@@ -0,0 +1,90 @@
---
id: IB-WP-0002
type: workplan
title: "Infospace Lifecycle Baseline"
domain: markitect
repo: infospace-bench
status: planned
owner: markitect
topic_slug: markitect
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_slug: "ib-wp-0002-infospace-lifecycle-baseline"
state_hub_workstream_id: "b5972baf-1fb4-4375-a8e3-6e6d6d6fb97c"
---
# IB-WP-0002 — Infospace Lifecycle Baseline
## Goal
Implement the first file-backed baseline for creating, loading, updating,
inspecting, and exporting infospaces.
## FRS Coverage
- FR-001 to FR-004: infospace lifecycle
- FR-010 to FR-012: knowledge artifact population
- FR-020 to FR-021: structure and relationships
- FR-070 to FR-071: export and derived artifacts
- FR-090 to FR-091: structured errors and explicit failures
## Tasks
### T01 — Define repo-local infospace layout
```task
id: IB-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "c8aaa52e-db89-42e3-9ebc-cb89be3f4d30"
```
- Define `infospaces/<slug>/infospace.yaml`
- Define artifact, output, evaluation, metrics, and report directories
- Document required and optional files
### T02 — Define configuration model
```task
id: IB-WP-0002-T02
status: todo
priority: high
state_hub_task_id: "a96c3439-89e4-40d0-8731-fe6b39a8f451"
```
- Reimplement the useful `markitect/infospace/config.py` concepts
- Keep references to schemas, workflows, sources, disciplines, and viability
thresholds explicit
- Avoid importing runtime orchestration concerns
### T03 — Implement artifact model and loader
```task
id: IB-WP-0002-T03
status: todo
priority: high
state_hub_task_id: "36ad8a84-f4fd-48ca-bc6f-94827ac03481"
```
- Model artifact identity, source path, type, provenance, and relationships
- Support deterministic loading from file-backed projects
- Return structured errors for invalid layouts
### T04 — Add lifecycle CLI
```task
id: IB-WP-0002-T04
status: todo
priority: medium
state_hub_task_id: "bfa70d92-c896-4133-8b93-0ece3e53c649"
```
- Provide minimal commands for create, inspect, add-artifact, and export
- Keep command outputs scriptable and traceable
## Acceptance
- A new infospace can be created from a template
- An existing infospace can be loaded and inspected
- Artifacts can be added and listed
- Invalid configs produce structured, visible errors

View File

@@ -0,0 +1,86 @@
---
id: IB-WP-0003
type: workplan
title: "Evaluation And Inspection Framework"
domain: markitect
repo: infospace-bench
status: planned
owner: markitect
topic_slug: markitect
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_slug: "ib-wp-0003-evaluation-and-inspection"
state_hub_workstream_id: "bc368ba0-9fd7-4821-a5d7-e5c301faa80a"
---
# IB-WP-0003 — Evaluation And Inspection Framework
## Goal
Reestablish infospace quality evaluation and inspection as first-class
application behavior.
## FRS Coverage
- FR-030 to FR-032: evaluation and quality assessment
- FR-040 to FR-042: inspection, exploration, and visualization
- FR-080 to FR-081: optional AI-assisted operations and context provision
## Tasks
### T01 — Port evaluation result concepts
```task
id: IB-WP-0003-T01
status: todo
priority: high
state_hub_task_id: "9bab4b20-3fef-469e-9ce2-f0db3e05e26a"
```
- Reimplement score entries, entity evaluations, metric values, snapshots, and
diffs from `markitect/infospace/evaluation.py`
- Keep serialization simple and inspectable
### T02 — Rebuild collection checks
```task
id: IB-WP-0003-T02
status: todo
priority: high
state_hub_task_id: "ee335d74-5be3-4b94-91e3-509486909f93"
```
- Recreate redundancy, coverage, coherence, consistency, and granularity checks
- Keep dependencies explicit for embeddings and relationship graphs
- Write results to reusable structured outputs
### T03 — Add viability evaluation
```task
id: IB-WP-0003-T03
status: todo
priority: high
state_hub_task_id: "d46b3429-37ef-4375-96e1-304eabf2cc13"
```
- Compare latest metrics to `infospace.yaml` thresholds
- Report pass/fail per threshold and overall viability
### T04 — Add relationship inspection output
```task
id: IB-WP-0003-T04
status: todo
priority: medium
state_hub_task_id: "de4f45e4-81a1-4ddb-98de-15e99ed5605a"
```
- Export relationship summaries and graph representations
- Support at least one textual output and one graph-friendly output
## Acceptance
- Evaluation outputs are structured and diffable
- Collection-level metrics can be produced for a sample infospace
- Viability can be computed from declared thresholds
- Relationship structure is inspectable without hidden state

View File

@@ -0,0 +1,81 @@
---
id: IB-WP-0004
type: workplan
title: "Reference Infospace Pilot"
domain: markitect
repo: infospace-bench
status: planned
owner: markitect
topic_slug: markitect
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_slug: "ib-wp-0004-reference-infospace-pilot"
state_hub_workstream_id: "8940a180-646a-4b20-b41f-c56719adfb0e"
---
# IB-WP-0004 — Reference Infospace Pilot
## Goal
Create the first maintained reference infospace in this repo, using
`markitect-main/examples/infospace-with-history/` as the primary migration
candidate.
## Tasks
### T01 — Decide pilot corpus scope
```task
id: IB-WP-0004-T01
status: todo
priority: high
state_hub_task_id: "5042482f-a14c-4ae5-8d1a-19039dc97010"
```
- Choose between a small purpose-built corpus and a pruned Wealth of
Nations/VSM corpus
- Record the decision in `docs/`
### T02 — Migrate configuration and methodology
```task
id: IB-WP-0004-T02
status: todo
priority: high
state_hub_task_id: "a0909309-775b-4220-94f5-6ca811d44caf"
```
- Adapt `infospace.yaml`
- Bring over metrics methodology and tutorial material where still valid
- Remove generated output bulk unless needed as fixtures
### T03 — Define source provenance and artifact policy
```task
id: IB-WP-0004-T03
status: todo
priority: medium
state_hub_task_id: "10c001a3-ce42-4f1b-8b9a-9965844a94cb"
```
- Record source origin, license/public-domain status where applicable, and
transformation history expectations
- Decide which generated outputs are committed versus regenerated
### T04 — Run first baseline evaluation
```task
id: IB-WP-0004-T04
status: todo
priority: medium
state_hub_task_id: "b5e43c2a-b29c-4cb6-b33c-b4db631d0079"
```
- Execute lifecycle and evaluation baseline from IB-WP-0002 and IB-WP-0003
- Save reports under the pilot infospace output structure
## Acceptance
- A concrete infospace exists in `infospaces/`
- The pilot demonstrates lifecycle, evaluation, and inspection behavior
- Migration from `markitect-main` is traceable and intentionally scoped