Proof Of Work

The style gate names which surfaces carry the first-person Operator register and holds every other page narrator-free until its re-voice, while rejecting weak connector prose, passive drift, and employer-implied narration everywhere.

Ladder role

Public prose moves from unstated register drift into named per-surface voice constraints.

Evidence artifact

scripts/verify-public-style-contract.js

Current checks

• npm run test:public-style

Next proof

Migrate each remaining surface into the Operator register until the narrator-free list shrinks to zero.

The identity gate pairs a named author with hard boundaries: personal handles, degree credentials, and social profiles stay off the public surface, employer representation stays excluded, and originality claims stay out.

Ladder role

Authorship moves from anonymous posture into a named author with explicit boundaries.

Evidence artifact

scripts/verify-public-identity-contract.js

Current checks

• npm run test:public-identity
• npm run build

Next proof

Keep disclosure language aligned across pages, feeds, and generated JSON.

The generator exports published pages, articles, axioms, builds, ladder placements, applied evidence, and proof receipts from one static contract.

Ladder role

Published site content moves into deterministic JSON for agents.

Evidence artifact

static/stoneytech-public-content.v1.json

Current checks

• npm run test:public-content
• npm run build

Next proof

Keep every new public artifact tied to receipt metadata before merge.

The site now exports a public graph linking pages, articles, axioms, builds, repositories, proof receipts, and the public MCP surface itself.

Ladder role

Published relationships move from implied navigation into an explicit graph for agents.

Evidence artifact

static/stoneytech-public-graph.v1.json

Current checks

• npm run test:public-content
• npm --prefix stoneytech-site-mcp test
• npm run build

Next proof

Add richer graph traversals and more visible human-facing proof chains on major pages.

The axioms page now names how StoneyTECH judges its own implementation: what holds, what is partial, and what proof still has to close.

Ladder role

Mission and axioms move from doctrine into a public scorecard judging the site itself.

Evidence artifact

/axioms#self-judgment

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Tighten the weakest partial areas until more mission checks can graduate from partial to held.

The build refuses article publication without a verification status matching the local verification log contract.

Ladder role

Publication claims move into code-enforced frontmatter and log checks.

Evidence artifact

scripts/validate-verification.js

Current checks

• node scripts/validate-verification.js
• npm run build

Next proof

Connect verification status directly to each public receipt record.

The axiom catalog gives recurring engineering judgment stable names, tiers, citations, and applied-evidence counts.

Ladder role

Repeated judgment moves from memory into explicit cited principles.

Evidence artifact

src/lib/data/axioms.js

Current checks

• npm run test:public-content
• npm run build

Next proof

Map more axioms to ladder rungs and receipt trails.

Reusable sidecars keep loaded terms short in prose while giving human and agent readers enough local context.

Ladder role

Definitions move from reader inference into local linked explanations.

Evidence artifact

src/lib/data/glossary.js

Current checks

• npm run test:public-content

Next proof

Add ladder-specific glossary links to proof and article sidecars.

The companion article maps AI stack levers to threat surfaces, citations, and mitigations before higher agency enters the design.

Ladder role

Capability choices pair with explicit attack-surface review.

Evidence artifact

/learn/2026-05-04-threat-surface-layer-by-layer

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Add a public matrix generator or reusable checklist.

The deployment-context article places cloud, sovereign cloud, private cloud, and air-gap constraints before model selection.

Ladder role

Model selection moves behind deployment constraints.

Evidence artifact

/learn/2026-05-11-deployment-context-first

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Add a public deployment-context selector artifact.

The essay turns MCP adoption into a decision ladder: static files, APIs, CLI tools, and narrower contracts first.

Ladder role

Tool choice moves through lower-cost alternatives before protocol adoption.

Evidence artifact

/learn/2026-04-27-cheaper-alternatives-to-mcp

Current checks

• npm run test:public-content
• npm run test:public-style

Next proof

Add a public decision matrix artifact or repository.

The essay separates learned style, retrieved facts, and prompt behavior so each concern carries a smaller boundary.

Ladder role

Voice and facts move to separate rungs instead of prompt improvisation.

Evidence artifact

/learn/2026-04-27-lora-plus-rag-composition

Current checks

• npm run test:public-content
• npm run test:public-style

Next proof

Add a runnable demo or public synthetic example.

The essay closes the graph around existing Ladder pieces by mapping task framing, current facts, repeated behavior, external action, prevention, and proof to their proper system surfaces.

Ladder role

Prompt work, context work, fine-tuning, tools, gates, and evals become placement choices instead of competing slogans.

Evidence artifact

/learn/2026-05-17-prompt-context-fine-tune-gate

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Add a small interactive placement selector or graph-readable decision table.

The graph article explains why explicit nodes, edges, budgets, and gates make agent loops inspectable before autonomy grows.

Ladder role

Agent flow moves from implicit emergence into explicit topology.

Evidence artifact

/learn/2026-05-03-graph-constrained-execution

Current checks

• npm run test:public-content
• npm run test:public-style

Next proof

Add a clean public graph workflow reference implementation.

The centerpiece comparison maps Anthropic TypeScript SDK, OpenAI Agents SDK, and LangGraph to three different agent jobs, with a matrix and selection tree.

Ladder role

SDK selection moves from fashion into job-shaped control-surface choice.

Evidence artifact

/learn/2026-05-05-three-sdks-three-jobs

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Wire companion README links and publish the clean-history public repository set.

The follow-up essay explains why the Trinity repos ship runnable examples, repo-local MCP stubs, file-backed graphs, and provider-binding seams so a reader can bring a model without losing the pattern.

Ladder role

Portable public pattern repos move control into local graphs, local MCPs, and templates before heavier infrastructure appears.

Evidence artifact

/learn/2026-05-06-portable-agent-pattern-kits

Current checks

• npm run test:public-content
• npm run build

Next proof

Promote one repo-local MCP from stub into a stronger read-only server and keep the compliance scan in the release path.

The follow-up essay explains why the Trinity repos begin with file-backed graphs, repo-local MCP reads, and explicit upgrade triggers instead of starting with hosted graph gravity.

Ladder role

Relationship knowledge becomes portable and inspectable in repo-local graph files before it graduates into larger infrastructure.

Evidence artifact

/learn/2026-05-06-local-graphs-first

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Promote one repo graph from file-only doctrine into a richer query surface once the repo-local MCP has real traversal pressure.

The follow-up essay explains why the Trinity repos expose shadow verifier panel seams, why second opinions should begin as non-blocking sentinels, and how weekly comparisons turn disagreement into evidence.

Ladder role

Second opinions move from intuition into named shadow roles, retained receipts, and explicit disagreement policy.

Evidence artifact

/learn/2026-05-06-shadow-verifier-panels

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Turn one shadow role into a real runnable comparison path with receipt-level disagreement output.

The source corpus names the ladder, its proof needs, page integration pattern, and maintenance rules before public presentation.

Ladder role

Site authorship moves into a single constraint system.

Evidence artifact

corpus/determinism-ladder.md

Current checks

• npm run test:public-content
• npm run build

Next proof

Keep corpus notes aligned with the public evidence ledger.

The ladder hub gives each AI system layer a rung, autonomy pattern, determinism purchase, failure mode, and receipt trail.

Ladder role

The core frame becomes public navigation.

Evidence artifact

/determinism-ladder

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Keep the proof ledger linked from the hub and public contract.

Each published article carries ladder metadata and a sidecar showing rung, trade, failure mode, and receipt links.

Ladder role

Page meaning moves from standalone prose into graph placement.

Evidence artifact

LadderSidecar.svelte and article frontmatter

Current checks

• npm run test:public-content
• npm run test:public-style

Next proof

Add per-article proof ledger backlinks on article templates.

Every build note carries ladder placement, public influences, axiom outcomes, and receipt references for agent-readable evidence.

Ladder role

Builds become receipts rather than a catalog.

Evidence artifact

src/lib/data/builds.js

Current checks

• npm run test:public-content
• npm run build

Next proof

Add public repository release links as clean-history repos go live.

The ledger turns the planning inventory into a public surface with status, ladder role, evidence artifact, checks, links, and next-proof gaps.

Ladder role

Receipts become browsable and agent-readable.

Evidence artifact

/proof-of-work

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Add live drift checks comparing deployed JSON, MCP responses, and page output.

The article and diagrams separate semantic graph meaning from hybrid persistence categories: relational, document, object, event, analytical, vector, search, cache, and ledger-style storage.

Ladder role

Graph-first doctrine moves from slogan into a vendor-neutral persistence placement model.

Evidence artifact

/learn/2026-05-17-graph-data-fabric

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Add a build note once a concrete public pattern repo implements the placement matrix.

The Learn article publishes the Discipline Patch technique and links the public repo built on public MITRE ATT&CK data.

Ladder role

Failed evals become corrective training examples for behavior, not facts.

Evidence artifact

/learn/2026-06-09-the-discipline-patch

Current checks

• verbatim body diff against package copy
• npm run test:public-content
• §1.5 grep before deploy

Next proof

Run the verification panel and keep the public repo link current.

The MCP primer explains the protocol in plain language and links the public StoneyTECH endpoint boundary.

Ladder role

MCP comprehension moves from assumed knowledge into a primer.

Evidence artifact

/demystify/2026-05-05-what-is-mcp

Current checks

• npm run test:public-content
• npm run test:public-style

Next proof

Keep endpoint docs aligned with the deployed public MCP URL and receipt tools.

The Learn article publishes the three permission tiers for agents in security operations and links the public GVAR engine logging every action as a cited, replayable event.

Ladder role

Agent permissions move from per-incident judgment into deterministic, auditable tiers.

Evidence artifact

/learn/2026-06-10-agent-authority-in-security-operations

Current checks

• npm run test:public-content
• npm run test:public-style

Next proof

Run the verification panel on the tier claims.

The Learn article publishes the open-tables detection CI argument, anchored by a shipped 250-rule gated-rollout platform, and links the Discipline Patch loop it shares.

Ladder role

Detection testing moves from a budget request into versioned fixtures run in CI.

Evidence artifact

/learn/2026-06-10-detection-as-code-over-open-tables

Current checks

• npm run test:public-content
• npm run test:public-style

Next proof

Run the verification panel; revisit when a lakehouse-native implementation is testable first-hand.

A five-minute argument for AI tilting the cyber offense-defense balance toward defense, earned not automatic, with the Fable 5 government suspension as the live case and a primary source behind every figure.

Ladder role

The cyber offense-defense question moves from hot take into a sourced, story-anchored argument about who builds first and who can revoke the tool.

Evidence artifact

src/posts/learn/2026-06-14-the-builder-goes-first.svx

Current checks

• npm run build

Next proof

Run the verifier panel to lift verification from pending-panel to panel-verified.

The MCP reads the generated public contract and exposes published content only: pages, essays, axioms, builds, repository notes, applied evidence, ladder placements, and receipts.

Ladder role

Published content moves into typed read-only MCP tools.

Evidence artifact

stoneytech-site-mcp/

Current checks

• npm --prefix stoneytech-site-mcp test
• npm --prefix stoneytech-site-mcp run build

Next proof

Finish clean-history public repo packaging and add live endpoint drift checks.

The public build note frames GVAR as citation-first learning from Google DeepMind Aletheia and Gemini Deep Think work, with no originality claim.

Ladder role

Editorial review moves from subjective trust into generator, verifier, refiner evidence.

Evidence artifact

/builds#gvar-engine-v2

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Publish a sanitized learning repo or paper-style explainer tied to public citations.

A verification-pipeline refinement: self-check runs reuse the same verifier-input shape as a full panel run, removing redundant generation.

Ladder role

Workflow topology moves from generator dependence into explicit branch purity.

Evidence artifact

Verification topology patch notes

Current checks

• prior panel receipt
• npm run build

Next proof

Add a public diagram and postmortem explaining the determinism gain.

The follow-up essay ties learning-agent, evidence-agent, and gvar-engine into one architectural claim: determinism moves into loop boundaries, evidence contracts, and explicit graphs as job shape changes.

Ladder role

A repeated thesis moves from selection advice into runtime-shaped proof.

Evidence artifact

/learn/2026-05-05-three-repos-one-thesis

Current checks

• npm run test:public-content
• npm run test:public-style
• npm run build

Next proof

Teach the portable agent pattern contract directly from the site and keep the repo-local MCP surfaces compliance-scannable.

The public MCP now exposes receipt lists and per-item receipt lookups while existing content tools retain ladder placement metadata.

Ladder role

Agent readers navigate by rung, trade, and proof receipts.

Evidence artifact

stoneytech-site-mcp/src/mcp-server.ts

Current checks

• npm --prefix stoneytech-site-mcp test
• npm --prefix stoneytech-site-mcp run build

Next proof

Add live endpoint drift checks against the deployed public MCP output.

The Builds page now records a governed-agent detection and response architecture, the approved measured prototype deltas, and the limits keeping the claim honest.

Ladder role

A private prototype proof point moves into a bounded public case study with explicit limits.

Evidence artifact

/builds/governing-an-autonomous-dr-platform

Current checks

• npm run test:public-content
• npm run test:public-identity
• npm run build

Next proof

Add a sanitized public reference repo or static diagram package when one is ready.

A future StoneyTECH public repo should package the read-only MCP, release manifest, negative-data contract, and smoke test from clean history.

Ladder role

Private implementation becomes a shareable learning package.

Evidence artifact

StoneyTECH org public repo plan

Current checks

• release manifest pending
• negative data contract pending
• smoke test pending

Next proof

Create clean public repository after private history scrub.

A future repo should show a synthetic generate, verify, adjudicate, refine loop with citations to Aletheia and no private workflow leakage.

Ladder role

Verifier-loop learning becomes a clean public reference.

Evidence artifact

StoneyTECH org public repo plan

Current checks

• README citations pending
• synthetic fixtures pending
• negative-data scrub pending

Next proof

Create clean public repo from synthetic fixtures and public citations.

A future repo should show deterministic graph state, replay fixtures, branch gates, and convergence receipts using synthetic examples.

Ladder role

Workflow convergence becomes a public reference pattern.

Evidence artifact

StoneyTECH org public repo plan

Current checks

• state-machine tests pending
• replay fixture pending
• convergence receipt pending

Next proof

Create the public graph workflow reference implementation.

A future CLI or small app should generate a layer-by-layer threat table with public OWASP and MITRE citation fixtures.

Ladder role

Threat modeling moves into a repeatable layer matrix.

Evidence artifact

StoneyTECH org public repo plan

Current checks

• citation fixtures pending
• snapshot tests pending

Next proof

Create a public generator with sample inputs and snapshots.

A future selector should map residency, security, latency, cost, and operating constraints before model or provider choice.

Ladder role

Architecture context moves into an explicit decision tree.

Evidence artifact

StoneyTECH org public repo plan

Current checks

• scenario fixtures pending
• residency checks pending
• cost checks pending

Next proof

Create a public selector with scenario fixtures.

A future package or recipe should publish the glossary data shape, sidecar component pattern, accessibility rules, and public export checks.

Ladder role

Vocabulary support becomes a reusable site pattern.

Evidence artifact

StoneyTECH org public repo plan

Current checks

• component tests pending
• accessibility check pending
• public glossary export pending

Next proof

Extract a clean package or documentation recipe.

A future ops receipt should cover D1 write reliability, compaction or rotation, and reconcile persistence for work claims.

Ladder role

Coordination reliability moves from implicit storage to monitored capacity.

Evidence artifact

coordination backlog plan

Current checks

• work-claim write pending
• reconcile persistence pending

Next proof

Close the D1 uniqueness drift and persist reconciliation evidence cleanly.