Skip to main content
.brik stores local BRIK64 project metadata. In Beta15.6, the CLI also writes selected workspace events to .brik/ledger/ so local activity can be checked as a tamper-evident hash chain. The public .brik workspace standard is published at brik64/brik-standard.

​
Typical Records

  • Logic events.
  • Ledger events in .brik/ledger/events.jsonl.
  • Ledger head pointer in .brik/ledger/head.json.
  • Export references.
  • Local decisions.
  • Evidence references.
  • Command metadata.
  • Generated artifact references.

​
What Belongs In .brik

Use .brik for operational metadata that helps explain what happened:

​
What Does Not Belong In .brik

Do not store:
  • secrets;
  • tokens;
  • raw private source snapshots;
  • unrelated personal data;
  • private account identifiers;
  • credentials or API keys.
.brik helps preserve traceability. It does not replace review of the PCD, Polymer or command output.

​
Ledger Commands

Use the ledger commands to inspect local workspace history:
Ledger verification fails closed when events are edited, deleted, reordered or when required ledger files are missing from an initialized workspace. The local ledger is not a distributed blockchain and is not a formal certificate. It is local tamper-evident workspace history.