Knowledge Work

Seventeen Principles of Knowledge Work

I am not a programmer. I am a knowledge worker: thirteen years professional in search engine optimization (SEO), information retrieval, and organization, and I have been instructing since I was five years old. The repositories linked on this page are my intuition codified. Judgment written down precisely enough that a machine can execute it and another person can pick it up and operate it.

That split is disclosed openly because the split is the product. I specify, judge, and correct. Models execute. Every repository here states how it was built: my specification and judgment, model execution, adversarial audit before anything shipped.

The principles

P01. Knowledge must leave the head. Private expertise cannot compound, transfer, or run while it stays tacit. Codification preserves the distinctions that make an expert's actions work, in a form that runs when the expert is absent.

P02. Own the memory plane. Vendor continuity is not owned memory if you cannot inspect, correct, export, or move it. Plain text is the default because it stays readable across applications, models, and vendors. Models remain replaceable workers; the record is yours.

P03. Continuity compounds. Retrieval selects the exact slice the present question needs. Accepted output returns to the corpus. Each turn starts on prior work, which is an advantage no amount of effort can reproduce when every session resets.

P04. Synthesis starts from sources. Writing begins with evidence, not an empty prompt. Gather, extract, compare, reorganize, curate. The portable seed is a context file: identity, context, instructions, constraints.

P05. Semantic order lowers retrieval cost. Structure begins with the central entity and its defining attributes. Hierarchy, contextual flow, and coverage determine whether a reader or a machine can retrieve the right answer without reconstructing it from fragments.

P06. Evidence outranks fluency. Runtime output, current files, and confirmed source text outrank recollection and convincing prose. A file is read before it is changed. Checkable claims keep their provenance; thin evidence carries an honest confidence label.

P07. The machine executes; the person judges. Models recombine a shared corpus. They do not supply the angle cut by one person's life, and they do not inherit accountability. Routine work runs unattended; consequential actions stay gated behind a human verdict.

P08. Build a modular person-system. Memory, reasoning, coordination, execution, and integration are separate layers. Any component can be replaced without erasing the operating contract or the record.

P09. Agency is governed. Meaningful work moves through a visible contract: pressure-test the spec, build, audit reality against the claims, then promote or revise. Side effects carry gates at the capability layer, not at the level of politeness.

P10. Production means persistence, bounded autonomy, and observability. A prototype becomes production when it survives interruption, runs its safe routine work, reports its condition, and can be repaired. Autonomy describes continuity of execution, not a transfer of accountability.

P11. Voice is a written standard. Taste made legible: corrections recorded as constraints, tests, and examples, so quality does not depend on policing every sentence by hand. Concrete language, natural rhythm, no generic model markers.

P12. Abrasivism gives persuasion its edge. Shane Hunter's direct-response philosophy: authentic voice, deliberate polarization, confidence transfer. The edge comes from perspective and a willingness to make a clear claim. It never excuses invented proof.

P13. LISEC turns expertise into a clear transformation. Joshua Lisec's teaching: source-first confidence, positioning, proof, de-risking. A title identifies the reader and what the reader gets. Promises stay inside what evidence can support.

P14. Authority is structured coverage over time. Koray Tuğberk Gübür defines topical authority through semantically organized coverage, historical data, and lower retrieval cost. I extend it past search: a person becomes authoritative by covering a field until they are the cheapest reliable path to the answer, for a buyer, a crawler, a model, or a collaborator.

P15. Perspective becomes products. Delivered service becomes durable material when the work is recorded, examined, and packaged. As models make remixing the shared corpus cheap, the scarce input is documented experience and the choices behind it.

P16. One person, one canon, many surfaces. Personal, business, and technical domains are one system wearing different clothes. Different rules and gates per surface, one philosophy underneath. The durable person-system: owned memory, producing roles, a written voice standard, a human review gate.

P17. The system learns through correction. A failure is not closed by an apology. It becomes a dated correction, enters the right instruction surface, gets tested, and stays active until revoked. Learning is inside the operating loop, not after it.

Named lineage: Abrasivism is Shane Hunter's philosophy, carrying Eugene Schwartz's image-word practice through Hunter. LISEC is Joshua Lisec's teaching, carrying Scott Adams's talent-stack idea through Lisec. The semantic and topical-authority principles are Koray Tuğberk Gübür's. The paid-message belief-shift bridge came out of a client collaboration in paid media. The integration architecture that makes these operate as one system is mine.

The repositories

Each repository attacks one named aspect of this system. Enter at any altitude; every road leads back here.

Repository Principles What it proves
observer-daemon P11, P17 Voice as an enforced written standard. A daemon that scores output against rubrics selected by content class, and a correction ledger that turns failures into active constraints.
vault-crawl P06, P10 Fail-closed acquisition and retrieval in Rust: checksummed migrations, fixture corpus, status and doctor commands that refuse to lie about their own state.
pretool-memory P02, P03 The owned memory plane: persistent file-based memory that survives across sessions and vendors.
safe-api P09 Governed agency: the capability-gate pattern that makes side effects a permission, not a habit.
web2md P04 Acquisition and normalization: sources in, clean portable text out.
observer-protocol P11 The written voice standard itself, as documentation. The doc companion to observer-daemon.
declip P10, P15 Production tooling proof: a working local audio pipeline.
subtlebodhi P05, P14, P16 The vault reference architecture: one canon, semantically structured for retrieval. Formerly published as scale-with-search; GitHub redirects the old name here.

The book

Uncorked is the long-form treatment: how thirteen years of client work became a codified system, with the receipts. The pointer lands here when the current revision ships; until that day, this page is the canonical map.

How this was built

Specification, judgment, taste, and every factual claim on this page: human. Execution of the repositories: AI models operating under the contracts described in P07 and P09, with adversarial audits before anything went public. If that division of labor bothers you, P07 is the argument; if it intrigues you, the repositories are the evidence.

I build systems that run operations.

AI infrastructure, search strategy, and the operational layer underneath both. If this is the kind of problem you're working on, get in touch.