TODO (example, delete): conversation-compaction-spike.md (LCORE-1314)

Spike for TODO: feature name

Overview

The problem: TODO

The recommendation: TODO

PoC validation: TODO

Decisions for TODO specify reviewer(s)

These are the high-level decisions that determine scope, approach, and cost. Each has a recommendation — please confirm or override.

Decision 1: TODO title

TODO: Context, options table, recommendation. Link to the relevant background section(s) below.

Option	Description
A
B

Recommendation: TODO

Technical decisions for TODO specify reviewer(s)

Architecture-level and implementation-level decisions.

Decision N: TODO title

TODO: Context, options table, recommendation. Link to the relevant background section(s) below.

Recommendation: TODO

Proposed JIRAs

TODO: One subsection per JIRA. Each JIRA’s agentic tool instruction should point to the spec doc (the permanent reference), not this spike doc.

LCORE-???? TODO fill in title

TODO: Use the format from docs/contributing/templates/jira-ticket-template.md. Change type above to Story if user-facing.

Description: TODO

Scope: TODO

• TODO

Acceptance criteria: TODO

• TODO

Agentic tool instruction: TODO

Read the "[section]" section in docs/design/<feature>/<feature>.md.
Key files: [files].

PoC results

TODO: If a PoC was built, document what it does, what it proved, and how it diverges from the production design.

What the PoC does

Important: The PoC diverges from the production design in these ways:

• TODO

Results

TODO

Background sections

TODO: Research and analysis that supports the decisions above. These sections are linked from the decisions, not read front-to-back. Common topics: current architecture, existing approaches, design alternatives. Add or remove as needed.

Appendix A

TODO: Supporting material — external references, responses to suggestions from team members. Add appendices as needed.