repo-first • deterministic executor • policy guardrails • verifiable compliance

AI can think. Stack Model lets it execute. Deterministic. Private. Policy-enforced. Built on 0xsigil's Automaton framework

Stack Model is a layered execution architecture transforming AI intent into verifiable state commitments. Cognition does not control custody. Execution cannot bypass policy. Capital cannot move without proof.

Buy $GITSTACK
Intent → Validate → Compile → (Proof) → SettleNo private-key exposure (smart account)SDK for strategy plugins
Create a post (demo)

This is local-only interactivity (no backend yet). Great for demoing "forum-like" UX.

Community feed

128
r/gitstack•pinned•1d

What is GitStack (quick version)

"A strategy repo + deterministic execution + policy guardrails + optional compliance proofs." MVP focus: repo + executor + policy checks + audit trail.

••
74
r/strategies•proposal•3d

Strategy repo: commits / PRs / reviews for on-chain execution

Clear history, reviewers, and policy checks. Strategies can be forked, merged, and audited.

••
52
r/security•deep dive•5d

Custody separation: execute via smart accounts, not shared private keys

Execution authority is delegated via programmable smart accounts with policy-bounded permissions.

••

Spec (raw)

A scrollable README-style section — concise, copy-paste friendly, and builder-focused.

Execution pipeline
pipeline
function executeIntent(intent):
  validated = policyLayer.validate(intent)
  if not validated:
    revert("Policy violation")
  executionPlan = automaton.compile(intent)
  proof = zkLayer.generateProof(executionPlan)  # optional
  settlement.commit(executionPlan, proof)

Deterministic state transitions: Intent → Validation → Compilation → Proof → Settlement.

Formal model
formal-model
Let:
  I = Agent Intent
  P = Policy Constraints
  C = Compiled Execution Plan
  π = Zero‑Knowledge Proof
  S = Settlement Function

Validation:  V(I, P) → {0,1}
Compilation: C = A(I)
Proof:       π = Prove(C satisfies P)
Commitment:  S(C, π) if V(I, P) = 1

Settlement only happens if policy validation passes.

Policy examples
policy
K ≤ K_max        # capital limit
σ ≤ σ_max        # volatility constraint
E ≥ E_min        # expected return floor
route ∈ whitelist
cadence ≤ max_frequency

Policies can be vault-specific, user-specific, or strategy-tier specific (public/private).

Modular SDK
@gitstack/sdk
@gitstack/sdk
- strategy plugins
- compiler adapters
- policy modules
- settlement adapters
- (optional) privacy/proof layer

Goal: let developers compose strategies without rebuilding custody and guardrails from scratch.

Request access

Drop your email for early access and build updates.

Tip: use Formspree / Google Forms / Supabase for a lightweight backend.

FAQ

7 questions

Common questions about GitStack, the execution model, and $GITSTACK.