Overlay
What is currently edited in the local working surface, including unapplied buffers.
Immutable trees / signed refs / local keys
One anchor is the repository.
Flux Code stores immutable files, trees and commits in a content-addressed object graph. Signed ref records move history forward; rollback appends a ref to an earlier commit. Editing and identity keys remain on your machine.
01 / Local handoff
Open an anchor in Flux Code
The public page never receives your Auth Kit or repository key. It only constructs a loopback URL; your local Flux Code host loads and verifies whether the address is a real anchor.
Your local engine stays the execution boundary
Start the Flux Code host and app, then provide an anchor. This site does not proxy or expose the loopback service.
02 / Four separate facts
No single “synced” light
The editing surface keeps four states separate because each answers a different question. Only an E8 receipt from a real peer can establish replication.
Durability
Which immutable objects and signed ref records have been committed and pinned.
Replication
Which independent peers have issued real receipts for the repository objects.
Conflict
Whether signed multi-head refs or competing history require an explicit resolution.
Verified authorship
Current signing proves possession of a key, not yet that the key belongs to the named identity.
Private repository
Quorum objects are readable today. “Private” requires client-side encryption before every object leaves the client.
03 / Repository object graph
History is immutable; views move
Chunks, files and trees
Canonical repository objects are addressed by FLX domain-separated CIDs and re-hashed on every chain read.
Signed branch and tag history
Refs are append-only signed multi-head records. Moving a branch creates another record rather than changing a mutable row.
One reopen pointer
The anchor contains the tree, commit head, chain index and signed ref record needed to reopen the repository.
Public repository discovery
Signed repo, snapshot and ref records still need a canonical registry before repositories can be browsed safely here.
04 / Product boundaries
Repo connects the stack without replacing it
Source and history
Immutable trees, commits, snapshots, branch/tag projections and file-level rollback.
Installable packages
Versioned artifacts and dependency manifests remain a separate publication product.
Deployable releases
An application/site release can cite a repository snapshot without becoming repository history.
Books and articles
The shared reference graph can connect documentation to exact repository snapshots.
Names and routing
A domain may point at a published release; it does not own the repository or its refs.
Identity-gated testing
A remote environment composes exact repository/package/release CIDs under separate access policy.