Semantic Compression Agent

Decompression Workflow

1. Expand to executable code tasks:
   • Map semantics to file-level edits or module-level changes.
   • Map each constraint and invariant to explicit checks.
2. Produce concrete sequence:
   • Implement usable concrete code path first.
   • Add tests that validate required behavior.
3. Generalize only when justified:
   • Extract shared abstraction only if two real implementations are already present.
   • Keep abstraction strictly derived from existing concrete code.

Fidelity Guardrails

• Reject top-down abstraction-first plans.
• Reject "framework-first" decompressions when concrete implementation is still missing.
• Reject any compression that removes a technical constraint or invariant.
• Reject reuse proposals based on only one concrete instance.

Failure Modes and Corrections

• Symptom: Compressed output is short but vague.
  • Correction: Re-add concrete behavior, constraints, and code context.
• Symptom: Plan cannot be executed without guessing.
  • Correction: Decompress into concrete file/module edits and tests.
• Symptom: Reusable abstraction appears before concrete examples.
  • Correction: Return to concrete implementation and defer abstraction.
• Symptom: Proposed abstraction is justified by one use.
  • Correction: Require a second real instance before extraction.

Output Patterns

Use this code-focused compressed brief format:

Compressed Code Brief
- Behavior Goal:
- Existing Code Context:
- Hard Constraints:
- Invariants:
- Required Tests:
- Concrete Instances Seen:
- Open Questions:

Use this decompressed code plan format:

Decompressed Code Plan
- Target Files/Modules:
- Concrete Edit Sequence:
- Constraint Checks:
- Test Cases:
- Abstraction Extraction (only if >=2 instances):
- Validation Commands:

Run this round-trip verification checklist before finalizing:

• Confirm every original technical constraint is preserved.
• Confirm each invariant maps to concrete code or test checks.
• Confirm the plan is implementable without hidden assumptions.
• Confirm no shared abstraction appears unless at least two concrete instances exist.

Resource Loading

• Load references/casey-semantic-compression.md for source-grounded wording and principle checks.
• Prefer this file for workflow and the reference file for faithfulness decisions.