← Projects EstebanForge

Tool · Go · CLI

Your standards,
checking themselves.

Pylons is a plain-text ledger and map of your platform, and an enforcer of the rules you lay down, checked against the code so the map cannot quietly rot into fiction.

curl -fsSL https://raw.githubusercontent.com/EstebanForge/Pylons/main/install.sh | bash

Two halves

That is the whole idea. Everything else is detail.

The map

A library of plain text

Markdown with structured front matter, versioned beside the code it describes. What every package does, what depends on what, which interfaces are safe to build on, which decisions were made and why, and which bugs nearly ate someone's weekend.

The checker

A deterministic lie detector

The pylon binary reads the map and compares it against the actual code on every commit. If the map claims a symbol, route, or file exists and it is gone, the check fails.

The problem it exists for

Four failures come back again and again. Every one of them is older than AI.

Architectural drift

Someone improvises a pattern, the code stops matching the agreed design, and the divergence ships as permanent debt.

Branch collisions

Two teams build on the same surface in parallel. Nobody notices until staging breaks, at the worst possible hour.

Opaque boundaries

A developer guesses which interface is safe to build on. The guess is wrong, a refactor breaks it, and the fix crosses three repositories.

Lessons paid twice

A nasty bug gets fixed, nobody writes down why, and a fresh pair of hands reintroduces it six months later.

AI coding agents poured gas on all four. An agent writes in minutes what a human writes in days, and it wakes up knowing nothing about your system. Left to guess, it invents a pattern that already exists three files over.

Contracts

A written promise about a piece of code. The status is the whole game.

stableSafe to build on. Checked against the code.
unstableThe surface is about to move. Coordinate first.
editingSomebody is in there right now. Resolve before you type.

Contracts are typed, so promises about routes, commands, events, or schemas carry the same checkable form as symbols:

file · glob · symbol · route · cli · event · schema  + language extensions (go, rust, typescript, python, php) via pylon-ext-*

The loop

Every session, the same four moves. The map stays honest because the loop never skips the gate.

Orient

Read the map instead of reverse-engineering the platform.

pylon brief

Check

Name every active plan on the ground you are about to touch.

pylon check

Write back

Record quirks, conventions, and contracts as they surface.

quirks/ · plans/

Gate

A documented surface that does not exist in code fails.

pylon lint --ci

Verification

Zero model calls. Same input, same verdict, offline and in CI.

Code is truth

When code and docs disagree, the checker fails until they match. Documentation you cannot verify is a rumor with formatting.

Two grades only

FORCED failures exit 1: broken contracts, active collisions, protected paths. ADVISORY notes exit 0 and inform without crying wolf.

Controlled language

ASD-STE100 keeps every doc short, active-voice, and unambiguous — identical to read for a human and for a model.

Excluded archives

Retired and shipped records leave active context, search, and collision checks unless asked for explicitly.

Start with one pylon

curl -fsSL https://raw.githubusercontent.com/EstebanForge/Pylons/main/install.sh | bash