Initial implementation

This commit is contained in:
2026-05-14 11:32:25 +02:00
parent 6fd1ff7581
commit 916a895a85
31 changed files with 1461 additions and 21 deletions

View File

@@ -0,0 +1,5 @@
# Evaluation Baseline
The evaluation baseline implements serializable score objects, evaluation
snapshots, snapshot diffs, deterministic collection checks, viability
thresholding, and relationship inspection with Mermaid export.

View File

@@ -0,0 +1,5 @@
# Lifecycle Baseline
The lifecycle baseline implements a file-backed infospace layout with
`infospace.yaml`, an artifact manifest, deterministic artifact loading, and a
small JSON CLI for create, inspect, add-artifact, and export operations.

View File

@@ -0,0 +1,41 @@
artifacts:
- id: source/prd-scope.md
path: artifacts/sources/prd-scope.md
kind: source
title: PRD Scope
provenance:
source_path: wiki/ProductRequirementsDocument.md
source_section: Scope Definition
relationships:
- type: supports
target: generated/lifecycle-baseline.md
- type: supports
target: generated/evaluation-baseline.md
- id: source/frs-requirements.md
path: artifacts/sources/frs-requirements.md
kind: source
title: FRS Requirements
provenance:
source_path: wiki/FunctionalRequirementsSpecification.md
source_section: Functional Requirements
relationships:
- type: supports
target: generated/lifecycle-baseline.md
- type: supports
target: generated/evaluation-baseline.md
- id: generated/lifecycle-baseline.md
path: artifacts/generated/lifecycle-baseline.md
kind: generated
title: Lifecycle Baseline
provenance:
source_path: workplans/IB-WP-0002-infospace-lifecycle-baseline.md
relationships:
- type: precedes
target: generated/evaluation-baseline.md
- id: generated/evaluation-baseline.md
path: artifacts/generated/evaluation-baseline.md
kind: generated
title: Evaluation Baseline
provenance:
source_path: workplans/IB-WP-0003-evaluation-and-inspection.md
relationships: []

View File

@@ -0,0 +1,6 @@
# FRS Requirements
The functional requirements describe externally observable behavior for
infospace lifecycle management, knowledge population, structure and
relationships, evaluation, inspection, workflow execution, export, AI
assistance, and explicit error handling.

View File

@@ -0,0 +1,7 @@
# PRD Scope
The product requirements define `infospace-bench` as the application layer for
concrete structured knowledge spaces. The repo should support creation,
population, evaluation, inspection, transformation, generation, and export of
infospaces while avoiding low-level markdown tooling and runtime platform
ownership.

View File

@@ -0,0 +1,24 @@
slug: bootstrap-pilot
name: Infospace Bench Bootstrap Pilot
topic:
name: Infospace Bench Bootstrap Pilot
domain: Knowledge Engineering Tooling
sources: artifacts/sources
disciplines:
- name: Infospace Lifecycle
path: artifacts/generated/lifecycle-baseline.md
schemas: {}
workflows:
- name: baseline-inspection
report: reports/baseline-inspection.md
viability:
redundancy_ratio:
max: 0
coverage_ratio:
min: 1
coherence_components:
max: 1
consistency_cycles:
max: 0
granularity_entropy:
min: 1

View File

@@ -0,0 +1,9 @@
metrics:
redundancy_ratio: 0
coverage_ratio: 1
coherence_components: 1
consistency_cycles: 0
granularity_entropy: 1
details:
artifact_count: 4
relationship_count: 5

View File

@@ -0,0 +1,24 @@
# Bootstrap Pilot Baseline Inspection
## Scope
This pilot exercises the new file-backed lifecycle and evaluation baseline
against a compact corpus derived from the `infospace-bench` PRD, FRS, and
initial workplans.
## Result
The pilot is viable under its declared thresholds:
- `redundancy_ratio`: 0
- `coverage_ratio`: 1
- `coherence_components`: 1
- `consistency_cycles`: 0
- `granularity_entropy`: 1
## Migration from markitect-main
Migration from markitect-main is intentionally staged. The large
`examples/infospace-with-history/` corpus remains the main reference candidate,
but this bootstrap pilot proves the successor repo's baseline behavior before
bulk corpus migration.