AI Hackathon · Platform Engineering

Sky Lattice

In nature, a snowflake is made of an ice crystal lattice. Sky Lattice is that structure for a Snowflake account.

Snowflake itself is a blank slate. Every customer, we rebuild platforms by hand — lately with AI chats that forget why. Sky Lattice is the layer under the copilots: blueprint + intent + decisions + deterministic plan. AI fills the forms; Terraform still ships the platform.

Intent Decisions Blueprint Terraform AI Front Door

The problem

Snowflake is a blank slate.
AI chats are amnesiac.

Today

  • Every customer rebuild starts near zero
  • RBAC, envs, zones = tribal knowledge
  • LLM + Terraform: works once, forgets why
  • Follow-ups reopen a new chat with TF state, not judgment

Cost

  • Weeks of senior time per engagement
  • Inconsistent security posture
  • Hard handoffs, harder audits
  • AI accelerates typing — not institutional memory

Insight

“Don’t replace the LLM. Put an ice crystal lattice under it.”

Codify the recipe. Capture the why. Let AI drive the forms — never invent production IAM from scratch each session.

What we built

Sky Lattice

An internal toolkit that turns “how we set up Snowflake” into a versioned product: blueprint + customer intent + durable decisions + deterministic plan — with Cursor/Claude as the optional front door.

Natural language → Skill + intent/decisions → platformctl plan → Terraform / Snowflake

Live story

Greenfield in minutes.
Brownfield without amnesia.

  1. Init Acme platformctl init + wizard → domains, envs, restricted finance
  2. Plan the lattice Deterministic object graph: DBs, zones, roles, warehouses
  3. Record the why Decision file: temporary exception, expiry date, rationale
  4. Come back later New chat opens the customer repo — not a blank brain

Why this wins

Not another chatbot.
Not another Terraform module dump.

AI where it belongs

Skills interview and edit intent. Policy blocks unsafe shortcuts. Apply stays deterministic.

Memory that survives sessions

TF state = what. Decision store = why. Intent = what we mean to run.

Repeatable with deviation

Same blueprint, different customer params and approved overrides — not copy-paste HCL.

Low friction for Snowflake people

Five verbs. Snowflake vocabulary. Familiar plan output. Optional agent IDE.

Who cares

Anyone shipping Snowflake platforms more than once.

Primary

  • Data platform consultancies
  • Internal platform / enablement teams
  • Multi-account Snowflake orgs

Pain they already feel

  • “We reinvent RBAC every client”
  • “AI helped, then we lost the thread”
  • “Brownfield is a black box”

Hackathon status

Working scaffold. Honest v0.

v0.1

Blueprint · platformctl · wizard · decisions · drift inventory · Cursor skill · demo customers

Next vertical slice

  • Live Terraform → Snowflake apply
  • Overrides that change the plan graph
  • Live account discover

The ask

Help us harden the lattice.

We’re building the control plane for AI-assisted data platform delivery. Join as design partners, Snowflake SMEs, or judges who’ve felt this pain.

Open source trajectory Consulting IP today Product tomorrow

Sky Lattice — structure under the copilots.

Sky Lattice 1 / 9 ← → or click