Closes the loop.
Reconciliation ensures that every action's outcome is verified against its intent. It is the mechanism that makes SpineWorkspace self-improving.
Reconciliation Flow
Execution Receipt → Re-ingestion → Normalization → State Update → Reconciliation → Discrepancy Handling → Memory Promotion → Next Work
Step 1: Execution Receipt
interface ExecutionReceipt {
id: string;
executionToken: string;
action: ActionDef;
status: 'success' | 'partial' | 'failure';
result: ActionResult;
timestamp: string;
}
Step 2: Re-ingestion
| Trigger | Re-ingestion |
|---|
| Write succeeded | Pull updated state from target system |
| Write partial | Pull partial state, flag discrepancy |
| Write failed | Log failure, no re-ingestion |
Step 3: Normalization & Entity Resolution
| Operation | Description |
|---|
| Schema mapping | Map target system fields to Spine schema |
| Entity resolution | Match to existing Spine entities |
| Deduplication | Merge duplicate records |
| Validation | Check data quality |
Step 4: State Update
The Spine is updated with normalized data:
- Entity state updates
- Event recording
- Decision recording
- Provenance tracking
Step 5: Reconciliation
interface ReconciliationReport {
executionToken: string;
intended: ActionDef;
actual: ActionResult;
match: 'exact' | 'partial' | 'mismatch';
discrepancies: Discrepancy[];
}
| Match Type | Action |
|---|
| Exact | Close, promote memory |
| Partial | Flag for review |
| Mismatch | Escalate, compensate |
Step 6: Discrepancy Handling
| Severity | Handling |
|---|
| Low | Auto-retry with correction |
| Medium | Queue for human review |
| High | Escalate immediately, compensate |
| Critical | Halt pipeline, alert admin |
Step 7: Memory Promotion
| Memory Type | Content |
|---|
| Success patterns | What worked, why it worked |
| Failure patterns | What failed, why it failed |
| Entity knowledge | New facts about entities |
| Process knowledge | Improved workflows |
Reconciliation Connects to