Skip to content

FAQ

Skylattice is easiest to understand through direct questions.

What is Skylattice used for?

Skylattice is used for two things today: running a local-first agent runtime with explicit governance boundaries, and studying a compact reference design for durable memory plus governed repo automation.

Is Skylattice a generic coding agent framework?

No. Skylattice is intentionally narrower than broad agent frameworks. It trades breadth for explicit approval tiers, tracked validation policy, Git-backed reviewability, and rollbackable change paths.

How do I verify Skylattice without API keys?

Follow the quick start, run doctor, run the smoke tests, run the validation suite, and compare your outputs with the public-safe samples under examples/redacted/.

Does Skylattice store memory in Git?

No. Private runtime memory stays under .local/. Tracked Git history stores docs, configs, prompts, release notes, and other reviewable system behavior.

What does Git-native governance mean here?

It means meaningful edits, validation rules, and promotion paths stay visible in tracked files and Git history. The project is designed so operators can review what changed and why.

Is Skylattice a hosted product?

No. It is a local-first runtime and reference repository, not a managed assistant service.

Where should I look for proof first?

Start with proof.md, the quick start, and the v0.3.0 Stable release page.