Skip to main content

ZeqGit

ZeqGit is the framework's own git + PDF repository. It's where the things you build — a chat, a CLI contract, a VS Code workspace, a workbench project — live as versioned repos, and it's wired into your Zeq identity so there's nothing extra to sign up for. Whatever you make on the framework has a home here, and every commit carries a proof.

What you get​

One account

Sign in to the framework and your ZeqGit account is auto-provisioned — one ZeqID, single sign-on, no second login.

Every project a repo

Opening a project creates a private repo; every file is versioned, over standard git with a full web UI underneath.

PDFs you can read

PDFs and docs open inline in the ZeqReader instead of forcing a download; large binaries use Git LFS.

Every commit anchored​

This is what makes ZeqGit Zeq: each push is stamped with a ZeqProof — HMAC(operator∣result∣zeqond)\text{HMAC}(\text{operator} \mid \text{result} \mid \text{zeqond}) — on a hash-linked sequence, each entry referencing the prior hash. So a repository's history isn't just git's own integrity; it's the framework's tamper-evident audit chain, on the same clock as everything else. Your code's history is provable the same way a compute result is.

How it fits together​

ZeqGit is a self-hosted git service fronted by a small bridge that ties it to the framework:

  • Identity / SSO — the bridge validates your framework session, provisions the matching git account, and signs you in transparently. Guests are redirected to the Zeq dashboard; the raw git login is never shown. One ZeqID is one ZeqGit account.
  • Repos & files — the bridge creates repos and commits files as you, so authorship and permissions are yours.
  • Reading — any file renders inline with the ZeqReader; permissions are enforced on every read.

Because your VS Code and Chrome workspaces name their repos through one shared module, the same project is the same repo across the editor, the browser, and the web — they never drift apart.