01
The problem
An AI conversation ends. A platform keeps living. Without a system, the next session starts from zero, decisions get re-made, mistakes repeat, and nobody can say what was checked before something went live.
Glass City Intelligence · The Glassforge system
Understand Glassforge.
Every decision kept. Every change checked. Every release proven. All of it without you watching over it.
Glassforge is the system Glass City Intelligence uses to build and run platforms with AI agents. It turns what used to need a team, a meeting and a good memory into something that happens on its own, the same way every time, with proof.
Built the PC NET TECHS website and PC NET DESK·Running strong since July 2, 2026
- 14Laws
- 51Working rules
- 34Lessons kept
- 2Workflow packs
- 3Platforms live
- 48Releases
Glassforge 1.37.0, October 14, 2026: fourteen laws; twenty-five shared rules, sixteen for the Wix-managed Astro stack and ten for the Vercel stack; thirty-four lessons; two workflow packs; three live platforms on one version; forty-eight numbered releases since October 5, 2026.
The short version
The problem, the answer, the result.
02
The answer
Glassforge gives the agents that build your platform a memory, a rulebook and an automatic path to production: plain files with a version number, read at the start of every session, with checks that run on their own.
03
The result
Your decisions stay decided. Every change is checked the same way. Releases happen by themselves, with proof. And the platform keeps getting better, release after release, without losing a thing.
New to software? Glassforge, simply explains it all in plain words and everyday examples.
01 · The problems it solves
Six problems every platform owner knows. One system that ends them.
Each of these is familiar to anyone who has had software built, by people or by AI. Glassforge was built to make every one of them stop happening, permanently, and to leave proof that it did.
Problem 01
Decisions that get forgotten
You decide something once. Weeks later it is quietly undone, because the person, or the conversation, that knew has moved on.
With Glassforge: Your decisions become laws: written in your own words, dated, read first in every session, and changed only by you.
Think of it asA constitution, not a conversation. It does not depend on who is in the room.
Problem 02
Every new helper starts from zero
A new developer, or a new AI session, needs days to learn how things are done here, and still misses half of it.
With Glassforge: One document per feature, ten headings, owning every file. The next agent starts informed, and a change to a feature must update its document, so the knowledge never goes stale.
Think of it asA ship’s logbook: the next watch takes over without waking the last one.
Problem 03
Mistakes that repeat
The same error happens twice, because the lesson lived in someone’s head.
With Glassforge: Every incident is recorded with its date and its cause. A lesson that should bind becomes a rule; a rule that can be tested becomes a check that runs on every change.
Think of it asAviation’s habit: every incident becomes a line on the checklist, and the checklist is why the next flight is safer.
Problem 04
Releases that depend on a person
Publishing means remembering the steps: the version number, the change log, the test, the search engines, the button.
With Glassforge: The merge is the release. The version is assigned by the system, the change-log row inserted, the site published, the search engines notified and a live page checked, all on their own.
Think of it asA canal lock: the boat goes in, the water does the lifting. Nobody carries the boat.
Problem 05
Nobody can prove what was checked
“It worked when I tried it” is not evidence, and a month later nobody remembers what was tested.
With Glassforge: Every change is a pull request; the checks run on the exact version being merged and are recorded with it; every release has its own row in a log that is never edited.
Think of it asA bank ledger: every entry dated, signed and never erased.
Problem 06
Two builders, one codebase, constant waiting
Two people on one project spend half their time asking who is doing what, and waiting for each other.
With Glassforge: Two agents work at the same time, neither waiting for or approving the other. Coordination is git and documents, and every commit is signed.
Think of it asTwo chefs in one kitchen with a shared recipe book and labelled stations. Nobody asks permission to cook.
02 · How it makes everything easy
You say it. It happens.
From your side, a change is one sentence. Everything after it, the reading, the building, the checking, the releasing, the verifying and the learning, runs on its own, the same way every time.
You say what you want
In plain words, once. A standing decision becomes a law; a task goes to an agent.
LikeBriefing a good contractor: you say what you want, not how to swing the hammer.
It reads before it builds
The agent starts by reading the laws, the project guide and the documents of the feature at hand: everything ever decided about it.
LikeA relief pilot reading the flight plan before taking the controls.
Every check runs by itself
The gates, the type check, the build, a real browser on every page at two sizes, the drift check, the document check, on the exact change, every time.
LikeSpell-check, grammar-check and a proofreader, all at once, on every page, every time.
The release happens by itself
Merge, and the version is assigned, the site published, the row recorded, the search engines told and a live page loaded as proof.
LikeA train on rails: the route is fixed, the doors open where they should, and nobody steers.
It checks its own work, live
The changed page is loaded on the live site, past the cache, and the new version’s own marker is found. Then, and only then, it is done.
LikeA chef tasting the dish before it leaves the kitchen.
It learns for next time
Anything that went wrong becomes a lesson, a rule and a check. The next change starts with more knowledge than the last.
LikeCompound interest: every lesson earns interest on the next.
What you never do again
- Choose a version number
- Write a change-log entry by hand
- Click “publish”
- Remember to tell the search engines
- Test every page on a phone and a desktop by hand
- Explain the project to a new helper
- Wait for one helper to finish before another starts
- Wonder what was checked before something went live
Four requests, as they happened.
October 14, 2026. The owner’s words, and what the system did with them.
Request 01
“Add /understand to the header navigation too.”
One pull request on this site: the navigation source, the header, the menus, the footer and the verifier’s own table. Checks green, merged, in production, minutes after the words were typed.
This site · one pull request · live in minutesRequest 02
“Re-render Glass City Intelligence and the concepts repo too.”
Two repositories moved their pin to Glassforge 1.37.0 and re-rendered their workflow files; the drift check proved every file matched; both merged and live the same afternoon.
Two sites · two pull requests · one afternoonRequest 03
“Block visitors from two more countries.”
On the client platform: the rule, its gate, its document and a change-log entry, the version assigned by the script; the merge published the site, inserted the row and notified the search engines.
Client platform · v5.126 · released within the hourRequest 04
“Make that change in Glassforge, then turn it back on.”
Two Glassforge releases the same morning, 1.36.0 and 1.37.0: the browser test now runs on the build inside the runner, so a preview makes no visit to the live site and a release makes exactly one. The client platform re-rendered and released as v5.124.
Glassforge 1.36.0 → 1.37.0 · v5.124 · the same dayOctober 14, 2026, in numbers: nineteen releases across four repositories, by two agents, every one a pull request with its checks green on the exact head — and every one recorded.
03 · The benefits
What you get, and keep getting.
A website, a customer portal, an internal tool, a whole product: under Glassforge it is built, released and improved with the same discipline, by agents that start every session knowing everything that has been decided.
01
Your decisions stay decided
Fourteen laws in your words, read first in every session; changed only on a pull request you merge.
Think of it asA constitution, not a conversation.
02
Nothing is ever lost
Thirty-four lessons, fifty-one rules and a document for every feature: the whole working knowledge of your platform, versioned, available to every agent in every session.
Think of it asA library that reads itself to every new visitor.
03
Proof, not promises
Every change is a pull request with its checks recorded; every release has its row, append-only. You can always see what was done, by whom, and what passed.
Think of it asA ledger: dated, signed, never erased.
04
Twice the hands, none of the waiting
Two agents on one codebase at once, independently. Nineteen releases across four repositories on October 14, 2026, by two agents.
Think of it asTwo chefs, one kitchen, labelled stations.
05
Robust. Extraordinarily reliable.
Glassforge built the PC NET TECHS website and PC NET DESK; the website has run on it, robust and extraordinarily reliable, every day since July 2, 2026.
Think of it asA good bridge: you stop noticing it, which is the point.
06
Improvements arrive on a cadence
A project pins a version; improvements reach it through a reviewed re-render, and a check proves every rendered file matches.
Think of it asYour phone’s updates: reviewed, scheduled, and proven to match the original.
07
It grows without getting heavier
Any stack is a pack; any number of projects pin the same version; another agent needs a name on the commit, not a seat at a meeting.
Think of it asA recipe scales to any number of plates.
08
Everything can be seen
Glassforge is a folder of plain files with a version number. Nothing hidden; everything can be read, diffed and verified.
Think of it asFittingly, for a glass city: glass walls.
04 · In production
Proven on three platforms. Current on every one.
Glassforge is not a proposal. It built the PC NET TECHS website and PC NET DESK, it runs the release process of three live platforms on two different stacks, and all three follow the same version: 1.37.0 on October 14, 2026.
Platform 01
Glass City IntelligenceVercel + Astro
This website. Vercel’s build is the gate: the isolation and authorship scans, the type check, the verifiers and the drift check run before anything deploys; GitHub’s handoff check reads what the build cannot see.
- 1
- reviewed workflow
- 7
- file roots owned
- 75
- feature documents
Platform 02
PC NET TECHSWix-managed Astro
Created with Glassforge: a managed-services company’s public website and PC NET DESK, its windowed admin platform, in production since July 2, 2026, robust and extraordinarily reliable. Twenty gates, the drift check and a browser test of every page at two sizes run on every pull request; the merge publishes the site, writes an append-only change-log row and notifies the search engines.
- 20
- gates
- 504
- checks a preview
- 45
- feature documents
Platform 03
A private concepts siteVercel + Astro
The studio’s client-concept websites, adopted in a single pull request: the isolation, drift, authorship and feature-document checks before the build and a browser test after it.
- 1
- pull request
- 4
- stages at once
- 2
- required checks
Forty-eight Glassforge releases between October 5 and October 14, 2026, each tagged and published by the workflow itself after its validator passed on the exact head. The 504 browser checks are one preview run of the Wix-managed platform on October 14, 2026: thirty-one pages at two sizes, no warnings.
05 · Under the hood
For the curious: how it works.
You never need to know this to benefit from it, any more than you need to know how a lock works to use a door. It is here because everything in Glassforge can be seen.
The four layers.
01 · Decides
The ownerLaws in the owner’s own words; the decisions that always return to the owner.
02 · Remembers
GlassforgeRules, lessons, feature documents, workflow packs and checks, one version at a time.
03 · Build
The agentsClaude Code and Codex: read, build, check, merge and release, independently.
04 · Run
The platformsThree today — websites and admin platforms on two stacks, all on one version.
Direction flows down as laws, rules and templates. Experience flows back up as lessons, rules and checks.
Six parts, all plain files.
Part 01Laws
The owner’s decisions, kept verbatim and typed by origin. L-001 to L-014. Read first in every session; changed only on a pull request the owner merges.
Part 02Rules
How the work is done on each stack: 25 shared rules, 16 for the Wix-managed Astro stack and 10 for the Vercel stack, with the order of authority as rule one.
Part 03Lessons
Every incident recorded with its cause, its date and the gate that followed. A lesson that should bind becomes a rule; a rule that can be tested becomes a check.
Part 04Feature documents
One document per feature, ten headings, owning every file. A pull request that changes a feature changes its document — and the check insists.
Part 05Workflow packs
Templates for a whole release pipeline, filled from one project file. Two packs today, Vercel + Astro and Wix-managed Astro; a new stack is a new pack.
Part 06Checks
Gates with consequences: authorship, isolation, drift, feature documents, commit trailers, the version, the change-log row, and a real browser loading every page at two sizes.
The cycle every change goes round.
01RequestThe owner’s words
02ReadLaws, guide, feature documents
03BuildOwn branch; code and document together
04CheckGates, build, browser, drift
05MergeThe exact head, checks green
06ReleasePublish, record, notify
07VerifyLive, past the cache
08LearnLesson, rule, check
Every change. Every time.And the next one starts with more knowledge than the last.
Two agents. No waiting.
Claude CodeIts own branch · its own pull request
Agent: claude-codeCodexIts own branch · its own pull request
Agent: codexThe required checks, on the exact head
mainEvery merge a release. Every release recorded.
No agent waits
Nothing requires one agent to receive anything from the other before it can start, continue, merge or release.
Git and documents, nothing else
A branch, a pull request, a merged main, a feature document, a commit trailer. What is in the repository is what exists.
Ownership by document
There is no “Claude’s feature” or “Codex’s feature”. Every feature has one document; whoever changes the feature updates it.
Every commit signed
Agent: claude-code or Agent: codex on every commit, checked on every pull request, so the record always says who built what.
What one pull request sets in motion.
On the pull request
Twenty gatesAuthorship scanDrift checkFeature documentsCommit trailerDescriptionVersion against mainType checkBuildA real browser, every page, two sizesMerge, which is the release
After the merge
PublishChange-log rowSearch engines notifiedOne live page loadedTag and releaseThe agent opens the pull request. Everything else happens on its own.
The full explainer, with the bounded details, is at /Glassforge.
06 · What it automates
An almost limitless range of repetitive work.
Anything that happens on every change, on a schedule, or the moment something occurs can be a template, a script and a check. Once it is, it happens every time, exactly the same way, with evidence. Think of a thermostat and a smoke alarm in one: it acts on a schedule, and the moment something happens. Here is what runs today, with no one lifting a finger.
On every pull request
- Twenty gates read the source
- The type check and the build
- A real browser loads every page at two sizes
- The drift check proves the rendered files
- Every changed feature’s document is checked
- The commit trailer and the description
- The version against main
On every merge
- The site publishes itself
- The change-log row is inserted, append-only
- Search engines are notified
- One page of the live site is loaded as proof
- A client site previews on its branch, releases from main and checks every page in a browser
- Glassforge tags and releases itself; a missed tag is recovered by the next run
On a schedule
- A heartbeat watches the client platform
- An outside pinger checks this site every fifteen minutes
- Search engines hear about changed pages every hour
- Visitor logs prune themselves at sixty and thirty days
- Admin access logs keep ninety days
- A render older than thirty days is flagged
The moment it happens
- A new lead is e-mailed, with retries, and pushed to the owner’s devices
- Visitors are told apart from bots at read time
- Traffic from blocked regions is refused before a page renders
- Analytics and Search Console data flow into the admin dashboards
- Monthly reports assemble from live data
- A month of social posts drafts itself on request
07 · The potential
Built for two agents and three platforms. Designed for far more.
Everything that makes Glassforge work for one platform is the same thing that lets it carry a hundred: the knowledge is files, the workflow is a template, the version is a number, and the agents coordinate through git.
01
Any stack
A pack is a folder of templates and one description file. The laws, the rules, the lessons and the renderer stay the same; a new host gets a new pack, and every project on it inherits the whole system.
Think of it asOne recipe book, any kitchen.
02
Any number of projects
A project pins a version and renders its workflow from it. The registry lists who follows what, a script reports who is behind, and every project is kept on the newest version, so a whole fleet moves together.
Think of it asA franchise’s operations manual: one edition, every location on the same page.
03
More agents
Coordination that is git and documents never gets crowded. The model is written so that an agent needs a name on the commit, not a seat at a meeting.
Think of it asMore chefs, the same labelled stations.
04
Knowledge that compounds
Every incident becomes a lesson, every lesson that should bind becomes a rule, every rule that can be tested becomes a check. The system gets stricter and smarter with every release: forty-eight so far.
Think of it asCompound interest, paid in checks.
How knowledge compounds.
An incidentSomething goes wrong onceRecorded with its date
A lessonIts cause, and what now prevents it34 lessons
A ruleA lesson that should bind51 rules
A checkA rule that can be tested20 gates on the client platform
One source, every project.
1.37.0Glassforge · one version
Render
Glass City IntelligenceVercel + Astro pack · 11 rendered files
Hash-lockedPC NET TECHSWix-managed Astro pack · 24 rendered files
Hash-lockedA private concepts siteVercel + Astro pack · 11 rendered files
Hash-lockedA hand edit to any rendered file fails the drift check. An improvement is made once, in Glassforge, and reaches every project through a re-render. Like a master key cut from one blank: every lock gets the same key, and a bent copy is spotted at once.
Glass City Intelligence
Give your ambition a system that carries forward.
Glassforge built PC NET TECHS and PC NET DESK, and the website has run strong on it since July 2, 2026. Tell us what you are building, and we will show you what it would make of yours.