Human-readable. Agent-ingestible. Owner-controlled.
SharePlane is my public sharing surface for essays, architecture, analysis, tools, patterns, and other finished artifacts. The work is designed for people first, structured so agents can understand it, and backed by enough context, caveats, and receipts for readers to make their own judgment.
Representative library
These artifacts span different subjects and forms, but they follow the same rule: make the argument readable, keep the evidence inspectable, and do not bury the useful part under the machinery.
Architecture Operating Model
SharePlane is a static publishing library and a governed context-as-code operating model. This artifact explains how versioned authority, human judgment, bounded agents, deterministic generation, validation, receipts, and exact-head publication turn rough ideas into durable public work.
Teaching Artifact Worked Example
A personal essay arguing that sustained cultural contact, not travel alone, can widen a narrow inherited worldview.
Teaching Artifact Worked Example
A source-derived architecture explainer separating personal second-brain markdown workflows from production agent context-plane requirements.
Teaching Artifact Worked Example
Article-first SharePlane thesis defining demo debt as the liability created when impressive AI demos are mistaken for supportable operational capability.
One system. Many visual languages.
SharePlane does not force every artifact into the same template. The shared identity, navigation, metadata, provenance, relationships, and receipts remain consistent. Inside that dependable boundary, each artifact is allowed to find the visual language that best serves the idea.
A personal essay should not look like a technical architecture. A calculator should not feel like an editorial argument. A visual teaching artifact should not be flattened into a generic content card merely because uniformity is easier to implement.
That variation is deliberate. The creative process is allowed to explore the probability field: different compositions, visual metaphors, typography, rhythm, density, and ways of making an idea land. Human judgment chooses the form. Creative Lock fixes the result.
Probability helps discover what the artifact can become. Determinism preserves what was chosen.
Consistency establishes trust. Variation keeps the work alive.
SharePlane is built as static files on purpose.
Simple systems are usually faster, easier to understand, easier to recover, and less exposed to failure or unnecessary cyber risk. A reader should not need a database, an application server, a dependency maze, or a consent banner merely to read an article.
A small build process does the complicated work before publication. The browser receives complete pages. The site remains portable, inspectable, cacheable, and rebuildable.
This is not a claim that every system should stay static forever. It is a refusal to buy tomorrow's complexity before today's need exists.
Complexity policy: Not until it is justified.
The publishing contract
The artifact leads. The design should make it worth reading, the structure should make it easy to understand, and the receipts should make it possible to challenge. No ads, trackers, feed manipulation, or machinery trying to become the main event.
The page has to work for a person before it earns the right to call itself agent-readable.
Presentation is part of usefulness. Serious ideas deserve clear hierarchy, deliberate design, and room to land.
Sources, claims, caveats, relationships, and receipts stay close enough to inspect.
I control what is published, how it is presented, and whether an ad appears. It will not.
Build-time automation, static files, and no backend until a real requirement earns one.
Why I built it
I like turning rough ideas, hard-won lessons, and occasional brain dumps into useful artifacts. I would not maintain a publishing machine that required endless manual formatting, CMS administration, or platform theater.
SharePlane is also a working demonstration of context as code. Versioned context, automation, validation, and receipts make the process repeatable enough to use in real life. This site is one implementation of the method, not a claim that every future need belongs on the same backend.
Keep the work useful, the evidence visible, the design beautiful, and the machinery on a short leash.