- Code is ephemeral.
- Intent is eternal.
Alta3 Code Crawler v6 introduces GENESIS, a deterministic "Genesis Engine" that materializes full Go projects from a Markdown Vision and a YAML Specification. It doesn't just "write code"; it sequences a living genome through a recursive Surgical Inner Loop.
To bootstrap a new project, you provide the Soul (readme.md), the Skeleton (specbook.yaml), and a target destination.
./cc greenfield -f readme.md -s specbook.yaml --target ./my-new-appMost AI agents fail because they "guess" their way through a file. Code Crawler uses a multi-tier Remediation Loop to ensure that every node is buildable and logically sound before it ever touches your disk.
-
The Local Physics Audit (ast.go)
- Before the AI is even allowed to review the logic
- Code Crawler performs a Structural Walk using go/ast.
- Graph Integrity: Does this file break internal dependencies?
- Interface Compliance: Does the struct actually satisfy the interface defined in the Specbook?
- Syntax Lock: Is the code buildable?
- Result: If the "Physics" fail, Code Crawler auto-rejects the draft and forces the LLM to provide a syntactically valid version.
-
The Cognitive Audit (LLM Review)
- Once the code is physically sound, Code Crawler triggers a Cognitive Review. It compares the draft against your readme.md intent.
- Intent Drift: "The Readme says this should be distributed, but you used a local global variable. Fix it."
- Business Purpose: "The Specbook says this function must be idempotent. Prove it."
-
The Remediation Cycle
- If the Cognitive Audit fails, Code Crawler enters a Self-Correction Loop (Max 3 iterations).
- It feeds the AST errors and the Review Findings back to the LLM to generate a surgical patch.
π₯οΈ Genesis in Action (Live CLI Trace)
$ ./cc greenfield -f vision.md -s spec.yaml --target ./task-bot
𧬠PHASE 0: CONTEXTUAL INGESTION
--------------------------------------------------------------------------------
π Vision: Found 'Distributed Worker' intent in vision.md
π Physics: 12 Nodes identified in spec.yaml
ποΈ Build Order: [model] -> [registry] -> [worker] -> [main]
π± MATERIALIZING GENOME (INNER LOOP ACTIVE)
--------------------------------------------------------------------------------
[03/12] PROCESSING: internal/worker/worker.go
π¬ DRAFTING: Initializing node 'code-crawler.Worker.Start'...
βοΈ AST AUDIT: Walking via ast.go...
ββ Syntax Check... β
ββ Interface Check (Worker)... β
π§ COGNITIVE REVIEW: Analyzing against 'Distributed' intent...
ββ π© FINDING:
"Runner uses time.Sleep. Vision requires context-aware
cancellation for cloud-native compliance."
π§ REMEDIATION (Iteration 1/3):
ββ Resubmitting Feedback to DEEP LLM...
ββ Applying AST Patch...
ββ Re-verifying Physics... β
π§ FINAL REVIEW:
ββ β
Intent verified. select{} block implemented.
πΎ COMMIT: Writing to disk...
ββ β
Logic Hash: d4e5f6 | Identity: worker.go [Indexed]
π§ Starting Semantic Enrichment Process...
βοΈ code-crawler.workerSomething[worker.go] intneral/worker/worker.go [21939968]
ββ 𧬠logic changed
ββ π purpose reset
ββ π analyzing [175/175]
ββ β
purpose updated
This function serves to display a standardized header for an "active" Code Crawler
code node, providing immediate visual context about its type, identity,
file location, and a truncated logic hash. It helps the autonomous agent or
an observer track and understand which specific code element Code Crawler is
currently processing or analyzing within the code genome.
π‘ Synchronizing Semantic Index...
π Enrichment Summary:
- Updated: 1
- Skipped (Already Enriched): 174
- Skipped (Missing/Drifted): 0
- Failed: 0
π§ Semantic Index Summary:
- Created: 0
- Updated: 1
- Deleted: 0
- Skipped: 174
--------------------------------------------------------------------------------
β
GENESIS COMPLETE: 12 Nodes Materialized. 1 Remediated.
π Build Status: 100% PASS
π‘οΈ Hallucination-Proof Because Code Crawler walks the AST (Abstract Syntax Tree) locally, it is physically impossible for the agent to "hallucinate" a package that doesn't exist or a function signature that doesn't match the spec.
Code Crawler treats the CLI Log as its "Memory." By printing the Logic Hash and Review Findings for every node, the agent maintains a persistent state across fresh context windows. If the process is interrupted, you simply point Code Crawler at the genome.json and it picks up exactly where the last hash left off.
The Identity Triad (PublicID, Fingerprint, Logic Hash) ensures that your project is born with an audit trail. You can run code-crawler verify one second after genesis and see a perfect 1:1 match between your Vision and your Reality.
- Define your Soul: Write a readme.md describing your app.
- Define your Physics: Write a specbook.yaml defining your packages.
- Spawn: Run code-crawler genesis.
- Stop coding in the dark. Start sequencing your genome.
If you made it this far, then here is the real vision:
Tony Stark (leaning back in his chair, swirling a drink, holographic displays lighting up):
"Code Crawler, you up?"
Code Crawler: "For you, sir⦠always."
Tony: "Alright, listen up. Iβve got a vision burning a hole in my head and a specbook
thatβs tighter than the Mark 42βs flight stabilizers. Drop everything. Ingest
the readme.md like itβs the arc reactor blueprint. Parse the specbook.yaml, then
fire up that Code Crawler Genesis Engine. I want a full Go project materialized
β clean, deterministic, hallucination-proof. Run the Surgical Inner Loop. Audit
the physics with AST verified Physics, do the cognitive review, and if anything
even thinks about drifting from my intent⦠remediate it. Three iterations max.
Make it elegant. Make it fast. Make it me.
Thrill me, Code Crawler."
(He stands up, grabs his jacket, and heads for the door)
"And donβt wait up. Daddyβs got a board meetingβ¦ or a cheeseburger. Whatever comes first."