ContextECF Suite

Level up from CodeLedger to the full Suite

The exact commands to check what's installed, get an install plan for FabricLedgerSDK and CFA, and verify everything is wired together — plus where self-serve currently ends.

1

Start with CodeLedger — fully self-serve, no token needed

This is the only layer that's a public, self-serve install today. Everything else in this guide builds on top of it.

npm install -g codeledger
codeledger init
2

Check what the Suite sees

Run this any time — it detects what's installed and tells you what to do next.

codeledger contextecf status

Example output

ContextECF Suite: partial
Privacy: local-first; source leaves machine: no; raw prompt export: no
  OK CodeLedger: 0.10.52
  MISSING FabricLedgerSDK: not detected
  MISSING CFA: not detected
Next:
  Install FabricLedgerSDK when agent-loop prompt governance is part of the evaluation.
  Install CFA when enterprise gateway policy and denied-capability receipts are part of the evaluation.
3

Get an install plan — this never installs anything by itself

install is deliberately explicit. It prints the real command and which environment variable it needs — it never runs npm, Docker, orgh for you, and it never prints the token itself.

codeledger contextecf install fabric --channel npm
codeledger contextecf install cfa --channel ghcr
ℹ️fabric and cfa are both protected channels — the token in the table below has to already exist in your environment. There's no self-serve signup for it yet; see the note at the bottom of this page.
4

Verify the pieces are actually wired together

codeledger contextecf doctor

Re-run contextecf status after any install — each component reports ready, degraded, or missing, with the specific next remediation step if it's not ready.

What each channel actually resolves to

ComponentChannelCommandAuth needed
FabricLedgerSDKnpm (recommended)npm install -g @contextecf/fabric-ledger-sdkNODE_AUTH_TOKEN(read:packages)
FabricLedgerSDKDocker sidecardocker pull ghcr.io/intelligent-context-ai-inc/fabric-ledger-sidecarGHCR_TOKEN(read:packages)
CFAGHCR (recommended)docker pull ghcr.io/intelligent-context-ai-inc/cfa-gatewayGHCR_TOKEN(read:packages)
CFAGitHub Releasegh release download v0.2.0 --repo Intelligent-Context-AI-Inc/CFAGITHUB_TOKEN(repo)

Where self-serve currently ends

FabricLedgerSDK and CFA are both protected channels — the auth tokens in the table above (NODE_AUTH_TOKEN, GHCR_TOKEN, GITHUB_TOKEN) aren't something you can generate yourself yet. If contextecf status shows them as missing and you want to move past that, tell us what you're working with and we'll issue the right access.

Want the full pitch first? See why teams layer FabricLedgerSDK and CFA on top of CodeLedger — the transaction spine, the adoption path, and concrete scenarios.