Demonstration
See how JCOOP journals operations and replays history under policy control.
Operation Recording
JCOOP doesn’t take snapshots. It records the operations that change your filesystem. Here’s a simple example:
CREATE report.txt
WRITE report.txt
DELETE report.txt
These three events are written to the journal in order. Each entry includes a sequence number, timestamp and path metadata.
Selective Restore
During replay you can exclude events via policy. Suppose we want to restore report.txt without the deletion:
# policy exclude deletes
policy:
exclude:
- operation: DELETE
# result after replay under policy
report.txt exists
JCOOP replays the CREATE and WRITE events but skips the DELETE. The journal remains unchanged; the policy lives outside the journal and is auditable.
Snapshots vs Journals
To appreciate the difference between backups and JCOOP, compare the questions each technology answers:
| Technology | Primary Question |
|---|---|
| Backup | What data can I recover? |
| Snapshot | What did the system look like? |
| Version Control | What changed in source code? |
| Log Aggregation | What messages were emitted? |
| JCOOP | What filesystem operations occurred? |
JCOOP complements traditional backups and snapshots. It doesn’t replace them. Instead it answers the question backups can’t: How did I get here?