WIP: save progress 2026-04-12
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Bill Holcombe
202
sprints/SPRINT-002-rsa-semantic-bootstrap.md
Normal file
202
sprints/SPRINT-002-rsa-semantic-bootstrap.md
Normal file
@@ -0,0 +1,202 @@
|
||||
# Sprint 002: RSA Semantic Bootstrap
|
||||
|
||||
## Status
|
||||
|
||||
Planned
|
||||
|
||||
## Intent
|
||||
|
||||
Define the first Whetstone-authored semantic model for `whetstone_RSA` and make it
|
||||
the new source-of-truth target for future RSA contract evolution.
|
||||
|
||||
This sprint exists to stop the project from continuing as a C++-first library by
|
||||
inertia.
|
||||
|
||||
## Problem
|
||||
|
||||
`whetstone_RSA` currently has a useful C++ scaffold, but the semantic center of
|
||||
gravity is still wrong.
|
||||
|
||||
The project has already concluded that RSA should be Whetstone-AST-first and that
|
||||
the C++ layer should be a runtime projection. That conclusion is documented, but it
|
||||
is not yet operationalized.
|
||||
|
||||
Right now:
|
||||
|
||||
- the semantic contract is still primarily embodied in `include/whetstone_rsa/types.h`
|
||||
- diagnosis/runtime interfaces are defined in C++ first
|
||||
- backend-selection and structured-slot support are planned but not yet represented
|
||||
in a semantic-first source model
|
||||
|
||||
If that continues, the bootstrap scaffold will become the architecture by default.
|
||||
|
||||
## Scope
|
||||
|
||||
This sprint is about semantic bootstrap only.
|
||||
|
||||
Primary outputs:
|
||||
|
||||
- a first concrete RSA semantic model
|
||||
- a mapping from the existing C++ scaffold into that semantic model
|
||||
- a projection boundary definition for future C++ runtime types
|
||||
|
||||
Supporting documents to update if needed:
|
||||
|
||||
- `docs/whetstone_ast_first_integration.md`
|
||||
- `ROADMAP.md`
|
||||
|
||||
This sprint does **not** require immediate deep changes to `whetstone_DSL`
|
||||
runtime code.
|
||||
|
||||
## Architectural Constraint
|
||||
|
||||
The semantic source of truth for RSA should live in Whetstone-authored forms.
|
||||
|
||||
The C++ code in `whetstone_RSA` should remain:
|
||||
|
||||
- runtime implementation
|
||||
- projected contract types
|
||||
- diagnosis/runtime execution machinery
|
||||
- backend adapter surface
|
||||
|
||||
It should not remain the primary authoring home of RSA semantics.
|
||||
|
||||
## Sprint Goals
|
||||
|
||||
### 1. Define the first semantic entity set
|
||||
|
||||
Establish the minimum initial semantic model for RSA:
|
||||
|
||||
- `DecisionContract`
|
||||
- `DecisionSurface`
|
||||
- `DecisionRequestModel`
|
||||
- `DecisionResultModel`
|
||||
- `SuitabilityAssessment`
|
||||
- `DiagnosisModel`
|
||||
- `ProbeDefinition`
|
||||
- `BackendSuitability`
|
||||
- `GatePackage`
|
||||
|
||||
### 2. Separate semantic contract from runtime behavior
|
||||
|
||||
Classify the current C++ scaffold into:
|
||||
|
||||
- semantic contract entities
|
||||
- runtime-only execution types
|
||||
- bootstrap/demo code
|
||||
|
||||
### 3. Define the first projection boundary
|
||||
|
||||
State clearly what will eventually be projected from semantic source into:
|
||||
|
||||
- C++ runtime contract structs
|
||||
- runtime manifests
|
||||
- schema artifacts
|
||||
- benchmark configuration artifacts
|
||||
|
||||
### 4. Prepare version-0 support for both enum and structured-slot gates
|
||||
|
||||
The semantic model must support:
|
||||
|
||||
- bounded enum outputs
|
||||
- bounded structured outputs with slots
|
||||
|
||||
from the beginning, even if early runtime examples are enum-dominant.
|
||||
|
||||
### 5. Leave RL/bandit as semantic placeholders only
|
||||
|
||||
Include `rl_policy` in backend-family semantics now so the contract stays open,
|
||||
but keep first implementation effort focused on:
|
||||
|
||||
- classical ML families
|
||||
- tiny transformer families
|
||||
|
||||
## Concrete Deliverables
|
||||
|
||||
### Deliverable A: Semantic model definition
|
||||
|
||||
Produce a concrete first semantic model with entity names, field groups, and
|
||||
relationship rules.
|
||||
|
||||
### Deliverable B: C++ scaffold mapping
|
||||
|
||||
Map the current public C++ surface into the semantic model, especially:
|
||||
|
||||
- `types.h`
|
||||
- `probe.h`
|
||||
- `probe_registry.h`
|
||||
- `diagnosis_engine.h`
|
||||
- `suitability_assessor.h`
|
||||
|
||||
### Deliverable C: Missing-field inventory
|
||||
|
||||
Identify what the current scaffold is missing for:
|
||||
|
||||
- structured slot outputs
|
||||
- backend suitability
|
||||
- deployment packaging
|
||||
- argument-oriented runtime invocation
|
||||
|
||||
### Deliverable D: Projection strategy
|
||||
|
||||
Define how future C++ types should be treated:
|
||||
|
||||
- temporary projection snapshots
|
||||
- not semantic source
|
||||
- updated from semantic-first changes rather than evolved independently
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- A first semantic model is explicitly documented in RSA docs
|
||||
- The model supports both enum and structured-slot gates
|
||||
- The current C++ scaffold is mapped into semantic vs runtime-only layers
|
||||
- Backend suitability and gate packaging exist in the semantic model even if not
|
||||
fully implemented in code
|
||||
- The roadmap and AST-first integration docs point to the same next step
|
||||
- A later session could begin implementing semantic-first RSA without re-deriving
|
||||
the architecture
|
||||
|
||||
## Not In Scope
|
||||
|
||||
- full implementation of semantic authoring inside `whetstone_DSL`
|
||||
- replacing the current C++ runtime scaffold
|
||||
- immediate automatic projection generation
|
||||
- training any model
|
||||
- wiring RSA into `whetstone_DSL` taskitem generation
|
||||
|
||||
## Case Study Rule
|
||||
|
||||
Use existing RSA C++ types and WhetstoneDSL decision surfaces only as evidence and
|
||||
bootstrap input.
|
||||
|
||||
Do not let any one case study define RSA semantics by itself.
|
||||
|
||||
## Recommended Execution Order
|
||||
|
||||
1. Inventory the existing C++ public surface.
|
||||
2. Define the minimum semantic entity set.
|
||||
3. Map each current C++ field into a semantic or runtime-only bucket.
|
||||
4. Identify missing fields required by version-0 goals.
|
||||
5. Define the projection boundary into C++.
|
||||
6. Record the next implementation step for semantic authoring.
|
||||
|
||||
## Exit Condition
|
||||
|
||||
This sprint is complete when the project no longer needs to answer:
|
||||
|
||||
"What is the first semantic model for RSA, and how does the current C++ scaffold
|
||||
map into it?"
|
||||
|
||||
That question should be settled well enough that implementation can start from the
|
||||
semantic model instead of revisiting architecture.
|
||||
|
||||
## Next Step
|
||||
|
||||
Represent the first three RSA semantic entities as Whetstone-authored forms:
|
||||
|
||||
- `DecisionContract`
|
||||
- `DecisionSurface`
|
||||
- `ProbeDefinition`
|
||||
|
||||
Then map `include/whetstone_rsa/types.h` onto those entities as a temporary C++
|
||||
projection target.
|
||||
351
sprints/SPRINT-003-whetstone-dsl-gate-semantic-bootstrap.md
Normal file
351
sprints/SPRINT-003-whetstone-dsl-gate-semantic-bootstrap.md
Normal file
@@ -0,0 +1,351 @@
|
||||
# Sprint 003: WhetstoneDSL Gate Semantic Bootstrap
|
||||
|
||||
## Status
|
||||
|
||||
Active
|
||||
|
||||
## Intent
|
||||
|
||||
Turn the current RSA architecture and gate inventory into an executable semantic
|
||||
bootstrap focused on the first concrete `whetstone_DSL` case-study gates.
|
||||
|
||||
This sprint exists to close the gap between:
|
||||
|
||||
- generic RSA architecture
|
||||
- generic semantic bootstrap language
|
||||
- actual `whetstone_DSL` decision surfaces
|
||||
|
||||
The output of this sprint should be concrete enough that later work can proceed
|
||||
without re-deriving what the first real gates are or how they map into semantic
|
||||
entities.
|
||||
|
||||
## Why This Sprint Exists
|
||||
|
||||
`SPRINT-002-rsa-semantic-bootstrap.md` established the architectural direction,
|
||||
but it is still too abstract to drive direct implementation.
|
||||
|
||||
We now have a concrete inventory in:
|
||||
|
||||
- `docs/case_studies/whetstone_dsl_gate_inventory.md`
|
||||
|
||||
The next step is to operationalize that inventory into:
|
||||
|
||||
- first concrete case-study gate records
|
||||
- explicit semantic mapping rules
|
||||
- clear enum-vs-structured-output boundaries
|
||||
- acceptance criteria for what counts as a completed bootstrap
|
||||
|
||||
## Scope
|
||||
|
||||
This sprint is still semantic-first.
|
||||
|
||||
Primary outputs:
|
||||
|
||||
- a detailed sprint plan for the first case-study gate set
|
||||
- semantic records for the first concrete `whetstone_DSL` gates
|
||||
- mapping notes from `whetstone_DSL` decision surfaces into RSA entities
|
||||
- explicit skeleton targets for later structured-output gates
|
||||
|
||||
This sprint does **not** require:
|
||||
|
||||
- model training
|
||||
- wiring RSA runtime into `whetstone_DSL`
|
||||
- replacing current `whetstone_DSL` heuristics
|
||||
- projecting full Whetstone-authored AST entities yet
|
||||
|
||||
## Primary Gate Set
|
||||
|
||||
These are the first concrete RSA case-study gates for bootstrap:
|
||||
|
||||
### Immediate RSA gates
|
||||
|
||||
- `verification_type`
|
||||
- `worker_type`
|
||||
- `prereq_op_selector`
|
||||
- `cpp_raising_profile`
|
||||
|
||||
### Skeleton-first semantic decisions
|
||||
|
||||
- `execution_contract_shape`
|
||||
- `workstream_grouping`
|
||||
- `target_file_selection`
|
||||
|
||||
## Gate Definitions To Lock Down
|
||||
|
||||
### 1. `verification_type`
|
||||
|
||||
Source surface:
|
||||
|
||||
- `RegisterArchitectIntakeTools.h`
|
||||
|
||||
Decision form:
|
||||
|
||||
- bounded enum
|
||||
|
||||
Expected outputs:
|
||||
|
||||
- `unit`
|
||||
- `schema`
|
||||
- `docs`
|
||||
- `smoke`
|
||||
|
||||
Contract interpretation:
|
||||
|
||||
- unstructured textual input
|
||||
- bounded discrete output
|
||||
- stable policy
|
||||
- deterministic downstream verification behavior
|
||||
|
||||
### 2. `worker_type`
|
||||
|
||||
Source surface:
|
||||
|
||||
- `TaskitemGeneratorV2.h`
|
||||
|
||||
Decision form:
|
||||
|
||||
- bounded enum
|
||||
|
||||
Expected outputs:
|
||||
|
||||
- `implementer`
|
||||
- `reviewer`
|
||||
- `architect`
|
||||
- `qa`
|
||||
|
||||
Contract interpretation:
|
||||
|
||||
- unstructured or hybrid textual input
|
||||
- bounded discrete output
|
||||
- mixed context sensitivity
|
||||
- deterministic downstream routing behavior
|
||||
|
||||
### 3. `prereq_op_selector`
|
||||
|
||||
Source surface:
|
||||
|
||||
- `TaskitemGeneratorV2.h`
|
||||
|
||||
Decision form:
|
||||
|
||||
- bounded structured output
|
||||
- factorized / multi-label candidate
|
||||
|
||||
Expected atomic outputs:
|
||||
|
||||
- `validate-intake`
|
||||
- `architect-review`
|
||||
- `resolve-dependencies`
|
||||
|
||||
Contract interpretation:
|
||||
|
||||
- hybrid semantic gate
|
||||
- not a good flat multiclass default
|
||||
- primary probe target for factorization analysis
|
||||
|
||||
### 4. `cpp_raising_profile`
|
||||
|
||||
Source surface:
|
||||
|
||||
- `RegisterCppRaisingTools.h`
|
||||
|
||||
Decision form:
|
||||
|
||||
- bounded enum
|
||||
|
||||
Expected outputs:
|
||||
|
||||
- `safe-first`
|
||||
- `perf-first`
|
||||
- `interop-first`
|
||||
|
||||
Contract interpretation:
|
||||
|
||||
- structured symbolic input
|
||||
- bounded discrete output
|
||||
- deterministic downstream execution and artifact generation
|
||||
|
||||
## Skeleton Decisions To Represent But Not Train Yet
|
||||
|
||||
### `execution_contract_shape`
|
||||
|
||||
Why skeleton first:
|
||||
|
||||
- output is structured
|
||||
- current semantics are implicit across many heuristics
|
||||
- not yet stable enough as a direct training target
|
||||
|
||||
Required semantic fields:
|
||||
|
||||
- target files
|
||||
- required tools
|
||||
- acceptance commands
|
||||
- step sequence
|
||||
- cross-project targets
|
||||
- resource locks
|
||||
|
||||
### `workstream_grouping`
|
||||
|
||||
Why skeleton first:
|
||||
|
||||
- current logic mixes lexical grouping with semantic bundling
|
||||
- good future structured-output gate
|
||||
- not yet clean enough for direct benchmark comparisons
|
||||
|
||||
### `target_file_selection`
|
||||
|
||||
Why skeleton first:
|
||||
|
||||
- current logic is bounded but still heavily heuristic
|
||||
- needs clearer contract and evaluation rules before training
|
||||
|
||||
## Deliverables
|
||||
|
||||
### Deliverable A: Case-study gate records
|
||||
|
||||
Update the semantic bootstrap so it explicitly records:
|
||||
|
||||
- gate identity
|
||||
- ontology fields
|
||||
- output labels or slot schema
|
||||
- candidate gate shape
|
||||
- deterministic baseline availability
|
||||
- downstream executor kind
|
||||
|
||||
for the four immediate gates.
|
||||
|
||||
Status:
|
||||
|
||||
- complete in `semantic/rsa_semantic_bootstrap_v0.json`
|
||||
|
||||
### Deliverable B: Mapping rules
|
||||
|
||||
Write down the mapping from current `whetstone_DSL` code surfaces into RSA
|
||||
semantic entities:
|
||||
|
||||
- `TaskitemGeneratorV2`
|
||||
- `TaskitemConfidenceAmbiguity`
|
||||
- `RegisterArchitectIntakeTools`
|
||||
- `RegisterCppRaisingTools`
|
||||
- `RoutingEngine`
|
||||
|
||||
Status:
|
||||
|
||||
- complete in `docs/case_studies/whetstone_dsl_semantic_mapping.md`
|
||||
|
||||
### Deliverable C: Structured-output bootstrap boundary
|
||||
|
||||
Define how `prereq_op_selector` and `execution_contract_shape` are represented
|
||||
without collapsing them into flat labels.
|
||||
|
||||
Status:
|
||||
|
||||
- partially complete
|
||||
- `execution_contract_shape` skeleton captured in
|
||||
`docs/case_studies/whetstone_dsl_execution_contract_shape_skeleton.md`
|
||||
- extraction rules for `prereq_op_selector` and execution-contract child
|
||||
decisions captured in
|
||||
`docs/case_studies/whetstone_dsl_gate_extraction_specs_v0.md`
|
||||
|
||||
### Deliverable D: Artifact-grounded extraction path
|
||||
|
||||
Define which surviving `whetstone_DSL` corpora can support RSA-aligned
|
||||
extraction, and which should remain context or evaluation corpora.
|
||||
|
||||
Status:
|
||||
|
||||
- partially complete
|
||||
- audit captured in `docs/case_studies/whetstone_dsl_run_artifact_audit.md`
|
||||
- first extraction rules captured in
|
||||
`docs/case_studies/whetstone_dsl_gate_extraction_specs_v0.md`
|
||||
|
||||
## Active Next Task
|
||||
|
||||
Turn the first extraction specs into machine-readable extraction contracts for:
|
||||
|
||||
- `prereq_op_selector`
|
||||
- `target_file_selection`
|
||||
- `acceptance_command_selection`
|
||||
- `required_tool_selection`
|
||||
|
||||
Status:
|
||||
|
||||
- partially complete
|
||||
- `prereq_op_selector` is now represented as structured/factorized in
|
||||
`semantic/rsa_semantic_bootstrap_v0.json`
|
||||
- `execution_contract_shape` skeleton is now defined in
|
||||
`docs/case_studies/whetstone_dsl_execution_contract_shape_skeleton.md`
|
||||
- `target_file_selection` and `workstream_grouping` still need explicit skeleton field sets
|
||||
|
||||
### Deliverable D: Probe-readiness notes
|
||||
|
||||
Record which probes should apply first to each gate:
|
||||
|
||||
- `confidence_threshold_probe`
|
||||
- `factorization_probe`
|
||||
- `schema_stability_probe`
|
||||
- `deterministic_rule_probe`
|
||||
- `context_width_probe`
|
||||
|
||||
Status:
|
||||
|
||||
- partially complete
|
||||
- immediate-gate probe candidates are recorded in the gate inventory and
|
||||
bootstrap notes
|
||||
- still needs a single consolidated probe-readiness artifact
|
||||
|
||||
## Recommended Execution Order
|
||||
|
||||
1. Extend the semantic bootstrap artifact with the first four case-study gates.
|
||||
2. Record mapping notes from each current `whetstone_DSL` implementation surface.
|
||||
3. Represent `prereq_op_selector` as structured/factorized rather than flat.
|
||||
4. Represent skeleton-only decisions for execution-contract shaping and grouping.
|
||||
5. Record which current gates should remain deterministic.
|
||||
6. Leave runtime wiring and training for later sprints.
|
||||
|
||||
Current progress:
|
||||
|
||||
- steps 1, 2, and 3 are complete
|
||||
- `execution_contract_shape` is complete enough for first-pass skeleton treatment
|
||||
- `target_file_selection` is now the active task
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- the sprint names a fixed first gate set rather than speaking about gates in the abstract
|
||||
- the semantic bootstrap artifact contains explicit records for:
|
||||
- `verification_type`
|
||||
- `worker_type`
|
||||
- `prereq_op_selector`
|
||||
- `cpp_raising_profile`
|
||||
- each gate is classified as enum, structured, or factorized
|
||||
- at least three skeleton-first decision entities are identified and justified
|
||||
- deterministic-baseline gates are explicitly separated from RSA gates
|
||||
- the sprint is actionable without reopening architecture debate
|
||||
|
||||
## Not In Scope
|
||||
|
||||
- training a new specialist
|
||||
- modifying `whetstone_DSL` runtime code
|
||||
- adding new RSA C++ runtime classes unless needed for semantic alignment
|
||||
- making Whetstone AST the full live authoring source this sprint
|
||||
|
||||
## Exit Condition
|
||||
|
||||
This sprint is complete when a later session can answer all of the following
|
||||
without ambiguity:
|
||||
|
||||
- what are the first real `whetstone_DSL` gates in RSA terms
|
||||
- which are enum versus structured-output
|
||||
- which should remain deterministic
|
||||
- which structured decisions need skeleton treatment before training
|
||||
- what the first semantic bootstrap records look like
|
||||
|
||||
## Immediate First Task
|
||||
|
||||
Extend `semantic/rsa_semantic_bootstrap_v0.json` with a case-study gate section
|
||||
covering:
|
||||
|
||||
- `verification_type`
|
||||
- `worker_type`
|
||||
- `prereq_op_selector`
|
||||
- `cpp_raising_profile`
|
||||
Reference in New Issue
Block a user