ulang-git · UI concepts · draft for the team

The forge, drawn as a world instead of a table.

Right now ulang-git proves every agent action, but the proof lives in a 100-row table. These five directions turn the same ledger into something a judge, a buyer or a new teammate gets in five seconds. Every number below comes from the live forge.

356 governed decisions 56 denied 2 landed on main 5 open claims rules b06f50e9 chain verified

Read from ztzkgit.northline-engineering.com on Oct 14, 2026, 9:30pm CT. The headline numbers are the forge's own. Scenes, extra repos, levels and most agent names are illustrative.

1 · The Archipelago

Every repository is an island, main is the harbor, and agents are boats. A claim is a boat tied to a dock nobody else can use. A denial is a storm cloud over the boat that tried. Idle agents drift to Dry Dock. Zoom out and the whole forge is one map.

best for: the demo video opener

HomeMapRulebook 8AgentsApprovals 1Storms 56

Harbor Log

2landed

5docked

56storms

ztzk-agent-5 tried a dock already takenStorm

robert approved a landing twiceStorm

Rulebook changed at #138New era

Landing waits on an ownerApprove

Before an agent sails, let me check the rulebook. Two boats never share a dock.

Why it worksLocks, denials and landings become physical: a dock, a storm, a boat sailing home. Nobody needs to know what a claim is.

Borrowed from the demoIslands as areas, a rest place for idle agents, dark name pills that survive zoom, a minimap, one helper character in the corner.

Built from real dataIslands = repositories. Docks = claimed paths. Storms = DENY decisions. The lighthouse = the active rule set.

2 · The Control Tower

µLang is air traffic control. Files are runways, agents are aircraft asking for clearance, and two planes never get the same runway. Each request shows up as a flight strip with the clause that cleared or held it.

best for: explaining the claim lock in 3 seconds

ztzk-agent → docs/**CLEAREDClaim granted. Path locked for this task, budget 3 of 4 left.

ztzk-agent-5 → docs/**HOLD · DENYRunway in use: another agent holds these files. ForgeClaim.claim_overlap

robert → land changeDENYThis landing was already approved once. ForgeLanding.approval_unique

tower log · today0 collisions356 requests judged · 56 held or denied · 2 changes landed safely.

jake → manage agentsREVIEW3 of 4 attempts denied in the last hour. Tower shows which clause each time.

● cleared● holding / denied● waiting on a humansweep = live ledger

Why it worksEveryone already understands that two planes can't use one runway. That is exactly the file claim lock.

The flight stripEach decision becomes one strip: who, what, verdict, plain-language reason, clause name underneath in mono.

For the pitch"Every Git platform asks who you are. Ours is the control tower that clears every move."

3 · The Agent Roster

Agents as a party of characters. Every card shows the four facts that matter, the claim budget as hearts (4, never refilled), a level that only rises when work actually lands, and the one human each agent answers to.

best for: Jake's "which human is responsible" goal

LV 3

🛠️

ZTZK-AGENT

Builder · writes and tests changes

STATUSOn a claim

TASKdocs smoke test

BUDGET❤️❤️❤️🤍

LANDED2

Answers to jake (human) · works only inside its own fork

LV 1

⚡

ZTZK-AGENT-5

Builder · new identity

STATUSDenied

TASKheld files

BUDGET❤️❤️🤍🤍

LANDED0

Answers to jake (human) · last stopped by claim_overlap

OWNER

👑

JAKE

Human owner · approves landings

STATUSOn duty

QUEUE1 approval

AGENTS2

RULEScan change

The only one who can change .forge/rules

REVIEWER

🔍

ROBERT

Human reviewer

STATUSActive

LASTapproved 1 landing

DENIED2 repeats

RULEone approval each

A second approval of the same landing is refused, by design.

The Bench Idle agents rest here. A claim that is still open keeps its agent awake, so unfinished work can't quietly go to sleep. 5 open claims resting

Why it worksBuyers think in people. A card with a human it answers to is the fastest way to say "these agents are accountable".

Honest statsLevel comes only from landed changes, never from activity, so the score can't be gamed by spamming requests.

Borrowed from the demoThe fixed four-tile status grid and the "line of command" under each character.

4 · The Case File

Jeff's "Decision Trace", styled as an evidence file. One change, its whole governed story on one page: every step, the verdict, the exact rule line that decided it, and the hash chain that proves nobody edited it after.

best for: answering "why was this allowed?"

change · agent-smoke-20261013061056

Create docs/agent-smoke file

✓ CHAIN VERIFIED · re-check

01 · CLAIM

Lock the files

PERMIT

02 · FORK

Private copy

PERMIT

03 · TOKEN

Key for seconds

PERMIT

04 · RUN

Sealed container

PERMIT

05 · LAND

Second approval

DENY

THE RULE THAT DECIDED IT

PROOF

#349←#350←#351←#352

Each record carries its own hash, the previous record's hash and a hash of the facts it was judged on. Change one byte anywhere and every link after it breaks.

FACTS IT WAS JUDGED ON

rules changed e50e43a0 → b06f50e9 at decision #138

Why it worksThe judges asked how you know why a change was made. This page answers it with the actual rule line highlighted.

Plain words first"Claim refused: another agent holds these files", with the clause name small underneath for engineers.

"What would make this pass?"Every DENY tells you the condition and which human can act. A denial becomes a next step, not a dead end.

5 · The Constellation

The ledger as a night sky. Every decision is a star, the hash chain is the line that connects them, denials burn red, and each rule-set era is its own band of sky. When the chain verifies, the whole constellation lights up. Tap a star.

best for: the hero shot and the investor deck

356

decisions in one unbroken chain. 56 red stars are denials. The violet line marks the rule change at #138.

Tap any star
Each one opens its decision: who asked, what for, the verdict and its clause.

Why it works"Tamper-evident hash chain" becomes something you can see: one continuous line through every decision ever made.

Scale storyAt 10,000 decisions it gets more beautiful, not more cluttered. The Lava Wall's big sibling.

InteractiveFilter the sky to DENY only, or one agent, and watch the other stars dim.

pieces that work in any of the five

Small ideas that make it feel alive

A helper in the corner

One character who checks the rulebook before you push and explains a denial in a sentence. Same job as the prompt helper in the demo, but for git.

A place for idle agents

Dry Dock, the Bench, a hangar. Inactivity becomes a place you can see, and open claims keep their agent awake.

One color, one meaning

Green only for PERMIT and Landed, red only for DENY, orange only for the main button. Fixes the "orange means everything" problem Jeff flagged.

Rule eras as a visible line

Every list, map and sky shows where the rules changed. It is the strongest proof that the rules govern the history.

Minimap + name pills

Dark pills that stay readable at any zoom, and a minimap with red marks where denials happened. The whole forge in one glance.

Click a red thing, get the story

A red lamp, storm, plane or star always opens the same Case File for that decision. One way in, everywhere.

Themes later

Same forge, different skins: islands, airport, space, a city at night. A buyer picks the world that fits their team.

The first five seconds

Open on the map with one boat getting stormed. No table until someone asks for it.

New repo that just works

Creating an island hands you a one-click first commit for humans and a copy-paste block for agents. Jake's next-round goal, made visual.

ulang.techPick a favorite and tell the team which one to build first.