Docs Getting started

How it works

Clone, validate, attest, promote — the four phases every commit walks through.

gridtrue turns the moment between 'I think it works' and 'I pushed it' into a cryptographic step. Four phases, all local until the last one.

1
1. Clone

git clone against your gridtrue remote pulls the code, the pinned validation environment, the policy contract and a scoped identity. The project boots on an empty machine in minutes.
```
git clone git@gridtrue.io:acme/payments.git
cd payments
gridtrue up
```
2
2. Validate

gridtrue validate executes build, tests and local deploy inside the pinned runtimes (container / native / VM) — on your machine. The result is a structured artifact, not scrollback.
```
gridtrue validate --profile=pre-push
```
3
3. Attest

If validation passed, the local runner signs the result with your enrolled identity and broadcasts the attestation to the org's private network. Teammates see it in real time.
```
# happens automatically after a green validate
gridtrue attest --last
```
4
4. Promote

git push checks the policy contract against the ledger. Commits without the required attestations cannot reach protected branches or environments — not because a CI server said no, but because the network never accepted them as valid.
```
git push gridtrue main
```

Who does what

Actor	Responsibility
You (developer)	Write code, run gridtrue validate locally, sign attestations with your OS-keyring identity.
gridtrue CLI + daemon	Executes validations in pinned runtimes, signs results, broadcasts attestations, subscribes to Conflict Radar events.
Your org network	Holds commits, attestations and policy decisions on an append-only ledger your organization owns.
Tech lead / architect	Authors the policy contract: what proof is required for which paths / branches.