Why SharePlane exists
Share useful work without renting the relationship.
SharePlane is my public, ad-free library for finished work. I control what is published, how it is presented, and what context travels with it. People can read it directly. Agents can consume the structured record. Neither gets to invent the missing evidence.
See the full system
The public page is only the visible layer.
RAG helps an agent find documents. Context as code helps a system know what those documents mean, which authority governs, what action is permitted, how work moves, what must be validated, and where human judgment remains mandatory.
How SharePlane Works explains the authority stack, human and agent roles, deterministic build, validation gates, context packages, and publication workflow behind the library.
See how SharePlane worksThe point
I wanted a place to share on my own terms.
Most publishing platforms are built around their incentives: feeds, ads, analytics, lock-in, or whatever growth ritual is fashionable that quarter.
SharePlane is simpler. I publish work that may help someone think, decide, learn, or reuse a pattern. The reader gets the artifact without popups, injected recommendations, or a page that shifts every time an ad loads.
Malott.ai holds my background, career evidence, and contact path. SharePlane holds the work itself.
What belongs here
Meaningful work, not content for content's sake.
SharePlane can hold technical explainers, architecture notes, source-derived teaching artifacts, personal essays, career lessons, community work, operating models, home infrastructure analysis, calculators, reusable patterns, and other finished public-safe artifacts.
The subject can change. The standard does not. The work should be clear, useful, visually considered, honest about what informed it, and strong enough to stand without an algorithm pretending it knows what the reader wants.
Context as code
This site is the method eating its own dog food.
I think in fragments, connect ideas, and produce a lot of raw context. Versioning that context, structuring it, and automating the mechanical parts of publication make it possible to turn those fragments into finished artifacts without building a small media company.
The process preserves source authority, locked copy, metadata, relationships, validation, and receipts as code. That makes the work repeatable, reviewable, and recoverable.
SharePlane is one implementation of the method. The architecture can evolve when a real requirement justifies it. Until then, the simple system wins.
Design philosophy
Deterministic where trust matters. Probabilistic where beauty belongs.
Facts, claims, dates, sources, caveats, relationships, receipts, and publication records should not drift. Those belong to explicit authority, deterministic generation, and mechanical validation.
Design serves a different purpose. It helps an idea become understandable, memorable, and worth spending time with. SharePlane therefore does not make every artifact wear the same visual uniform.
Each artifact can have its own composition, typography, rhythm, diagrams, visual metaphors, and interaction model. The shared shell provides identity and orientation without flattening the work inside it.
The design process is intentionally exploratory. Generative systems can search a wide probability field and surface forms that a rigid template would never produce. That freedom is useful before publication, not after it.
Human judgment selects the design. Creative Lock freezes the approved copy and visual direction. The implementation is then versioned, validated, rebuildable, and reproducible.
Probability explores. Judgment decides. Determinism preserves.
The architecture is part of the point
Complexity has to earn its place.
The old KISS principle still applies: keep it simple, stupid. Not simplistic. Not careless. Simple enough to understand, operate, secure, recover, and change.
A small build process creates the catalog, indexes, provenance graph, discovery files, and receipts before publication. The browser receives complete pages. The site remains portable, inspectable, cacheable, and rebuildable.
This is not a claim that every system should remain static forever. It is a refusal to buy tomorrow's complexity before today's need exists.
The machinery exists. It simply knows its place.
Rebuildable by design
A SharePlane deployment can disappear without taking the work with it.
The canonical artifacts, metadata, relationships, and receipts live in versioned files. The public site can be regenerated and moved to another static host without reconstructing a hidden database or reverse-engineering a proprietary content system.
Platforms are useful. Dependency is optional. Recovery should be boring.
What this is not
Not a content farm. Not an ad surface. Not a platform pretending to own the work.
SharePlane is not a runtime AI system, RAG stack, social network, personalization engine, analytics product, or machine for publishing every thought that survives contact with a keyboard.
It does not need accounts, behavioral tracking, sponsored interruptions, or a backend assembled from twelve services to display an essay.
The library exists for finished work. The machinery supports the artifact. It does not become the attraction.
Public-safe by design
Useful does not mean careless, and receipts do not make the work unbiased.
Every author has a point of view. Pretending otherwise is marketing, not rigor. SharePlane bounds that problem by separating claims, sources, caveats, and provenance where the artifact warrants it.
Raw private inputs stay out of the public site. Employer material, client information, controlled documents, personal identifiers, account details, security-sensitive implementation traces, and other restricted source material do not become public evidence merely because a model can summarize them.
Published artifacts may use public sources, approved personal notes, generalized professional experience, synthetic examples, derived calculations, and redacted or aggregated material. The public record should make that boundary clear without exposing the protected source itself.
When support is incomplete, the artifact should say so. Missing evidence is a recorded gap, not a permission slip for confidence theater.
How to read it
Start with the artifact. Open the evidence when you need it.
The main page is the work. Read the argument, use the tool, inspect the diagram, or follow the analysis first.
The artifact record, public sources, relationships, and receipt are nearby for readers who want to test the evidence boundary or reuse the work. They support judgment. They are not a tax on ordinary reading.
The Explore page provides human-friendly views by topic, format, and author. The Data page explains the machine-readable surfaces for agents, search engines, and other tools.Author note
Beautiful is part of useful.
I have always cared about how information is rendered, whether it is an image, a document, a diagram, or a page of HTML. Good design creates hierarchy, reduces friction, and gives serious ideas room to land.
SharePlane is a side project with a serious standard. It will grow as time permits, and features will be added when they solve a real problem, not because modern websites apparently collect features for sport.
Visit malott.ai ↗