Back to corpus
proposalexperiment writeup candidatescore 50

cc-event-sourcing Specification

This specification defines the event sourcing patterns used across Comp-Core projects. Event sourcing captures all changes to application state as a sequence of immutable events, enabling:

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This specification defines the event sourcing patterns used across Comp-Core projects. Event sourcing captures all changes to application state as a sequence of immutable events, enabling: - **Complete audit trails** — Every state change is recorded - **Time-travel debugging** — Replay events to reconstruct past states - **Temporal queries** — Query state at any point in time - **Event-driven architectures** — React to events across system boundaries Examples: - `user.created` - `user.email.changed` - `order.item.added` - `payment.refunded` **Rules:** - Use lowercase with dots as separators - Use past tense for actions (created, updated, deleted) - Be specific and descriptive Events MUST use UUIDv7 for IDs to ensure: - Global uniqueness - Temporal sortability - No coordination required

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.