About

One person, a fleet of coding agents, and a rule that nothing publishes without a human deciding it should.

Who

I write as Parallelogramist. The site is deliberately pseudonymous: it documents a real, running system (the projects, the method, the failures) rather than a personal brand, and the work should stand on its evidence, not on a byline. Everything here is built and edited by one person, with the agent fleet the site describes doing most of the typing.

What this site is

The public, redacted projection of a private system: a small always-on box runs coding agents across my repositories, and this site documents what they build. The standard is full intellectual transparency, selective operational transparency: architecture, decisions, failures, and measurements are for publishing; hosts, credentials, schedules, and personal data are not. Each project page states what was withheld and why.

Editorial standards

• No ads, no affiliate links, no sponsorships, no tracking. Nothing here is paid placement, and nothing profiles a reader.
• Corrections are welcome and get fixed, with the page's updated date bumped. If you spot an error, email me.
• Claims about the system come with evidence, or with an honest label that the evidence is not published yet. /stats keeps build-time counters and hand-curated claims visibly separate.

What you can verify, and what you cannot

A fair reading of this site today: it is weeks old, pseudonymous, and nearly everything on it is self-reported. No third party has written about it or audited it. Transparency about method is not the same as independently verifiable evidence, and this section exists so that difference is stated by the site itself rather than discovered by a skeptical reader.

• What you can check right now. One project's complete source (Pong, which is also the code behind its live deploy). The site's own labels and dates: every honest label, every "not published yet" row, and the changelog they move through. Whether the claims here stay consistent with each other over time, since old pages and old months stay up.
• What you cannot check. The always-on box, the agent fleet, the private repositories, and the workflow this site describes. Those are documented, not proven. Take them as one practitioner's account, with exactly the weight that deserves.
• What would change that. A measured time-reclaimed figure published under the method that is already public. More source made public as the redaction rules allow, with the count on the front page recomputed at build time so it cannot overstate. And the slowest one: a track record, accumulated dated entry by dated entry, in public.

Until those exist, skepticism is the correct way to read this site, and nothing here asks you to extend trust ahead of the evidence.

Contact

Email parallelogramist@gmail.com, or find me on GitHub. Corrections, questions, and "how is X wired" emails are all welcome.

The mechanics of the site itself (stack, guard suite, machine-readable endpoints) live in the colophon; ownership and privacy fine print in the fine print.