07 — Revocation & Compensation
Atomic rollback + compensation logic
Revocation in an append-only system works through compensation — recording that a
previous action is no longer valid, rather than deleting it.
Revocation Model
- Delete Records FORBIDDEN
- Modify History FORBIDDEN
- Compensate ALLOWED
- Revoke Forward ALLOWED
Compensation Types
- KEY_REVOKE POLICY
- POST_RETRACT SOCIAL
- KARMA_ADJUST MERIT
- FORK_ABANDON GOVERNANCE
Revocation Actions
Select a revocation type and provide the target identifier.
Revocation History
No revocations recorded.
Compensation Simulator
Simulate a compensation scenario to understand how it would affect the system state.
Atomic Rollback
In append-only systems, "rollback" means creating a new state that compensates for all effects of the target action and its dependencies.
RollbackPlan {
targetPulsar: string, // Hash of action to compensate
affectedPulsars: [], // Dependent actions
compensations: [ // List of compensation pulsars
{
type: "COMPENSATE",
original: string,
effect: "NEGATE" | "ADJUST"
}
],
newState: object // Resulting system state
}
NOTE: Rollbacks do not delete history. They add compensating
entries that make the original action effectively null.