The context-v corpus
Real context files.
Unedited.
1,305 specs, plans, issues, and the rest, written by one small agency while shipping 43 projects with AI agents. Nobody tidied them up for you; that's the point. Browse by the folder a file lives in, or by the project that wrote it.
The practice and the Claude Code plugin live at context-v.dev →
- Files
- 1,305
- Projects
- 43
- Kinds
- 33
- Last collated
- Nov 2, 2026
The flow, in files
Every file here was written somewhere in one cycle. Explorations open it: research until the question is clear. Then decide, spec, plan, and build, as a team or solo. Issues close it: what broke becomes the reminders, blueprints, and agent skills the next cycle starts with. Click a folder to read every file of that kind.
By kind
Prep
Deciding what to build, in descending altitude.
specs/140What is being built and why. Living documents, revised as the work changes.plans/125Sequenced, scoped work plans: closer to execution than a spec, not yet step by step.prompts/122Step-by-step implementation documents, each pointing back at the spec it serves.Reflection
What the system already knows, kept where agents can load it.
blueprints/71How and why a system is designed: patterns and architecture an agent must respect.reminders/100Short corrections born from the same AI mistake made twice.agent-skills/147Executable know-how in the Agent Skills shape: a SKILL.md an agent can load and follow.Journey
The path, written down while it was still unclear.
explorations/126Thinking out loud where the destination is unclear, until a spec is possible.issues/121The winding path through a hard bug, written down so nobody retraces it.Experimental tier folders still finding their shape
By project
·Recently changed
Make Every Repo in the Tree OKF Compliant
61 context-v bundles, 1,083 docs, most now OKF compliant. What's done, what's left, and how to finish the rest.
Lossless Citation Standards — Schema, Audiences, Portability Thesis
The schema layer: what fields exist, why each exists, and how they outlive any one rendering target. The WHAT and WHY, not the HOW.
The Lossless Citation Open Specification
Hex codes instead of numerics so pasted sources never collide — plus exact spacing and the Claude cited_text blockquote the web strips.
Plan: Retrofit Every Repo to OKF, Then to the Kit's Frontmatter
The kit made every doc declare a type. 945 older docs across 47 repos don't, yet. Here's the sweep that fixes it.
Maintain Project Task Management with LFM
One checkbox line that reads correctly in Obsidian and on GitHub, and only becomes queryable data when LFM is asked.
Preferred Format for Changelog
Astro Knots Skills Live in Two Places, and Will Diverge
The skills that define how we build Astro sites are split between lossless-agent-skills and astro-knots, and astro-knots-mcp is about to copy them into every new site. One canonical home, and a corpus that ingests it once.
Maintain an Authors List that Enables Naming Aliases
One person, many spellings: Michael Staton, Michael P. Staton, mpstaton. An authors list with aliases makes every byline resolve to one person.
Survey: a Scoped Dashboard of context-v
One command turns every context-v/ folder in scope into a dashboard, a task list, and a map, the way graphify turns code into a graph.
No Scripts for Frontmatter Edits
One wrong line in a script becomes a thousand broken docs, and every site and vault that reads them breaks at once. Agents edit by hand.
Create Study Everything as Code
Study Kickoff — Content Authoring Tools
Maintain an Elegant Open Graph System
A scalable, consistent architecture for Open Graph metadata optimized for the messaging-first share economy.
Maintain Base Engagement Analytics
Page views say someone arrived. Time on page, scroll depth and downloads say whether they read it. One definition of each, for every site.
Maintain Privacy Gates in Three Modes
One gate, three doors: a shared passcode, a verified email on the firm's list, or a link minted for one person. Each opens only what it names.
Handoff — Metafetch 0.2.0: Built, Pushed, Waiting on an In-Obsidian Check and a Release
Metafetch 0.2.0 is on development: the og:image fix, the 1.13 upgrade, folder profiles with socials, and any-model fields. Nothing is released yet.
MemoPop Connector API, Phase 7: The Plugin and Real Claude
A thin skill that keeps Claude on the method, packaged with the connector, and a test where real Claude writes the fixture memo.
MemoPop Connector API
Ten tools, one step registry, and the docs and tests that ship with each. What we build so a partner's Claude can write a MemoPop memo.
Claude connectors need didi.sh to be an OAuth server
didi.sh knows who a person is. It can't yet tell Claude so, and MemoPop's connector is the first product waiting on that.
OAuth Authorization Server for Claude Connectors
Discovery, authorize, token, refresh, and client registration on id.didi.sh, so Claude can sign a partner into MemoPop with one magic link.
Host the Connector on Railway at memopop.didi.sh
The connector gets its own subdomain pointed straight at Railway. No domain to buy, and no proxy in front of streaming.
jj Versions Text, and a Save Snapshots to the Bucket
Every draft is versioned without the client touching version control, and a single save backs the whole workspace up.
No Tool Ships Without Its Docs and Tests
MemoPop's connector is our first API, so it sets the habit: every tool has docs written for agents, CI tests, and a live health check.
One Workspace per Firm, with a Private Bucket
Each client firm gets one workspace on our server holding all its deals, plus a private bucket of its own for originals and backups.
Sign In Through didi.sh OAuth
Partners sign in once with their didi.sh account, and the token says which firm they belong to. didi.sh has to grow OAuth first.
The Client's Claude Does the Work
In v1 we pay for almost no model calls. The partner's own Claude writes the memo; MemoPop supplies the method and keeps the work.
The Server Hands Claude the Method One Step at a Time
Claude never holds the whole pipeline. It asks for the next step, does it, hands back the artifact, and asks again.
Three Kinds of Error, and Optional Steps Never Block
A blocked memo is the worst outcome. Every error says whether MemoPop is down, the request is wrong, or the step can be skipped.
MemoPop as a Claude Connector
Clients won't open our app. They'll ask Claude, and Claude will reach their deals, sources, and memo history through a connector.
Run the Connector Plans with a VP Eng and Subagents
One VP Eng holds the spec and the ledger; engineer subagents each take a plan from failing tests to green, changelog, and push.
MemoPop Connector API, Phase 1: Foundation
The registry, errors, auth, storage, five tools, the docs generators, the ledger, and CI. Every later phase builds on this one.
MemoPop Connector API, Phase 2: Deploy
A container with every system tool the memo needs, running on Railway at memopop.didi.sh, watched by a health check every 30 minutes.
MemoPop Connector API, Phase 4: Materials
Decks, datarooms, notes, and links reach the server three ways, become text the steps can read, and never block the memo.
MemoPop Connector API, Phase 5: Enhancements, Compile, and the Full Flow
Every enhancement becomes a step that can skip, compile turns sections into a branded PDF, and a scripted client walks the whole memo.
MemoPop Connector API, Phase 6: History and Snapshots
Every saved artifact becomes a jj change the client never sees, and one save backs the firm's whole workspace up to its bucket.
A Syncbox for Client Document Folders — Where Does History Actually Live?
The ask is one product. The prior art says it's three layers, and nothing on the shelf does all three on a bucket.
The Corpus Splash as a Reading Room
The practice has its own site now. This one stops selling it and starts showing it: a thousand real context-v files, by kind and by project.
Phase 2 — The Workspace and the Files Surface
Flave opens a folder, shows you what is in it, and lets you edit the theme that styles what you are reading — so design work is brought in once and reused, never recreated.
Fetching Content Updates is Multi-Step, Multi-Module
New content reaches lossless.group only after it moves through three repo levels and three branches. Skip a step and the site serves stale content.
Blueprint — Model Recipes: Any LLM API, Configured the Same Way in Every Plugin
One way for every Lossless plugin to call any model: a data-only recipe per provider, keys in Obsidian's keychain, and the same settings rows.
Handoff — Upgrading the Remaining Plugins to Obsidian 1.13 and the Current Stack
Three plugins down, seven to go. The to-do list, commands, and traps from shipping Image Gin, Cite Wide, and Perplexed in one day.
Plan — Migrate the Lossless Plugin Family to Obsidian 1.13
Obsidian 1.13 changed how settings render and get searched, and pnpm 11 changed where its settings live. One playbook, nine plugins, each still standing on its own.
Splash rollup:sync fails from where the operator actually stands
`pnpm rollup:sync` errored at the ai-labs root (no such script) and inside splash/ (pnpm 12 ignored the build allowlist). Both fixed.
Maintain Themes and Modes Across CSS and Tailwind
Implementation blueprint for dual-axis theme and mode control using Tailwind CSS v4 custom properties, with runtime utilities and Vitest verification.
New Site Quickstart Guide
Step-by-step guide for scaffolding a new Astro site in the astro-knots monorepo, from empty directory to working markdown rendering.
Issue: Enriching the Lossless Vault's 75 Citations with Promotion's Metadata Pipeline
We ran the new canonical-source pipeline over every citation in the vault. It filled 49 reference texts and 63 publishers, and found five bugs.
Plan — Upgrade Cite Wide to Obsidian 1.13 (0.3.0)
Cite Wide's commands stopped loading on Obsidian 1.14 and pnpm 12 wouldn't build it. One pass gets it loading, building, searchable, and tested.
Enrich Citations
One command fills in every citation's missing title, author, date, publisher, and brand assets — and shows you every change before it writes.
Promote to Canonical Source
One command turns a source you'll cite again — a book, a report — into a rich record with its file and full text in your vault.
Issue: Recraft Generation Froze Obsidian, and the V4.1 Upgrade
Recraft billed 40 credits and returned an image, then Obsidian locked up before saving it. The fix also moves Image Gin onto Recraft V4.1.
Plan — Migrate Image Gin's Settings Tab to Obsidian 1.13's Declarative Settings API
Half of Image Gin's settings silently vanished in Obsidian 1.14, and none were searchable. Rebuilding the tab on Obsidian's declarative API fixes both.
Amend "Untouched": Allow a Scoped Dependency Refresh of the Current Site
The rebuild is paused and the build time hurts every content push. The current site can take dependency upgrades, provided its rendering stays the same.
Context-V Is an OKF Profile
Any tool that reads Open Knowledge Format can read a context-v folder. The price is one frontmatter field and an index file.
Context-V as a Portable Plugin Any Agent Can Install
A human pastes one line, and their agent does the rest. The last mile of the cv plugin is an install contract written for agents, with Claude Code as the first harness, not the only one.
Agent-Native — Profile
The chat isn't bolted onto the app. The app's operations are one action registry that the UI, the agent, MCP, A2A and the CLI all call, and the conversation is just one more caller.
Build Time Too Long
A push takes about two minutes to deploy, but Astro compiles the site in six seconds. The rest is probably refetching content from scratch.
The MVP Delta, and What 'A Version Per Audience' Actually Requires
The editor half of the MVP is mostly built. The half that is the product, one document published to several audiences with proof that nothing leaked, has no code yet, two underspecified mechanisms, and one syntax in the spec that does not parse.
Handoff — the delta to MVP, 2026-10-03
Read this first if you're picking up flave. The editor works. The part that is the product, one document published to several audiences with proof nothing leaked, has no code yet. Here is that work, in order, with the decisions that gate it.
Explore Collaborator Codebases for Insights — Comparative Highlights
When a friend has built their own agentic-coding silo next to ours, compare the silos both ways: what we can learn from them, and what they can learn from us.
Gitignored Build Caches Must Ship to Vercel
A cache that is gitignored does not exist on Vercel. On an on-demand route that means live fetches inside the request and a write to a read-only disk.
A component test whose fixture is simpler than its call sites
Selector--Menu's suite was green while both of its first two adopters were broken in exactly the way its header promises to prevent.
Adopt Selector in one member
The test comes before the refactor. This is the first organ whose defects are invisible — a broken keyboard renders perfectly.
The list-surface paradigm — CardRow, ListContainer, and where selection lives
Sixteen of eighteen members are the same shape: controls up top, a generated list below. Five decisions are open; the BEM rollup makes most of them reversible.
A silently ignored alias pointed a verification probe at production
rsbuild accepts source.alias and ignores it. Three agents rendered live data believing it was a fixture; one wrote a file into client corpus.
Issues raised by the migration subagent while converging request-reviewer
Findings surfaced while doing something else. Raised, not chased — the diff stays clean and the finding stays reviewable.
Structural invariants live in prose, so sweeps stop halfway and nothing notices
Three units have now been found whose typecheck had never once passed. Each was found by accident, five weeks apart, by someone tidying something else.
The federation has no layout layer, so seven of its eight deviations are about placement
The design system standardised everything that goes inside a box and nothing about the boxes. Consumers keep their freedom for now — deliberately, and on the record.
Adopt CardRow and a SelectWrapper in one member
The pilot executor. Three members answer the open decisions with evidence; everything mechanical is inherited from the Button loop.
Adopt the shared Button in one member — the per-member executor for the Button rollout
One member per run, never a sweep. Replace the buttons, delete the recipes they made redundant, raise everything else.
Adopt the shared Chip in one member
The per-member executor for the Chip rollout. Inherits every probe and verification rule from the Button loop; what differs is the judgement about what a chip even is.
Converge the federated design system — scan members for organs, fingerprint them, and triage divergence into five verdicts
Creativity is the default and stays the default. The loop's job is to notice when two teams solved the same problem twice without meaning to.
Setting up a micro-frontend with the monorepo configurations it actually needs
Three live remotes shipped without a registry row and were invisible to every check for months. This is the list that prevents the next one.
The federal layer never shipped --space-*, --radius-* or --z-* — so ten members invented token names and let the fallback carry the value
170 declarations across the federation reference tokens that do not exist. Each one silently ships its literal in all three modes.
sort-filter-lens leaks 61 unnamespaced classes into every other remote — and .error, .row and .muted are live collisions today
One member ships 511 lines of global CSS with no root-class containment. Sixteen other surfaces render a class it restyles.
Two palette steps share one hex, so dark-mode borders measure 1.00:1
graphite-700 and graphite-800 are both #232634. Four federal boundary findings came out of one member's probe; three survive adjudication and one does not.
Submodule pointer bumps belong at wrap-up
Augment-It as Working App and Architecture Demonstration
Augment-it is a working product and a live architecture showcase at once; every decision answers to both lenses so neither quietly wins.
The Gap Between What We Preach and What We Practiced
Forty deployable units, one git repo, zero component-level design systems or changelogs. An honest audit of augment-it against the three recommendations we make to clients.
Build an Upgrade Ladder Cart from Superset Tiers
Make every tier a strict superset of the one below and the cart can show you the delta instead of swapping in a whole new cart.
Orient Before You Introduce a Term of Art
A reader who does not yet know what the thing is cannot learn its name. Plain question first, clinical title second — enforce it in the schema.
Webhook as Wake-Up, Not as Truth — relaying platform events into CI without trusting them
Polling gets throttled and push payloads are unsigned. Forward the interrupt, not the claim, and both problems stop mattering at once.
Every Step Writes Its Output To File
A run's destination folder is decided before the first step, and every step writes its result there as it finishes. Nothing lives only in memory.
Normalize Labels Gradually
One company says Total Revenue, another says Gross Revenue, a third says Top Line. One reports monthly, another quarterly, another H1/H2, another only annually. Collection never touches any of it. Normalization is a later, corpus-level act — a cluster of labels that mean the same thing, one chosen default, and an alias map — built by a person from real analysis across real portfolios, never by an agent guessing from what the words sound like.
Round-Closing Timeline Nuances
Wires arrive before and after the close they belong to, rounds close later than anyone planned, and a fund and its SPV subscribe months apart on identical terms. None of that is an anomaly. Record every date as the document states it, never revise one to make a sequence tidy, and confine anomaly-noticing to the handful of series that are actually real at this stage — money spent, web traffic, signed contracts, billed subscription revenue. Everything else is a claim or a projection, and instinctive concerns about it belong in anomalies.json rather than in the memo or the conversation.
The Sidecar Port Is Adopted, Not Owned
Tauri probes 8787 and uses whatever answers. A stray dev sidecar becomes the app's backend, silently, and the app looks fine.
Automerge — Profile
The only entry where two people editing the same paragraph is a solved case rather than a second file with a longer name — and it costs you the filesystem.
git-annex — Profile
Content is optional. git tracks which copies exist where, and refuses to drop the last one — the bookkeeping that makes deleting a local file safe.
Jujutsu (`jj`) — Profile
The storage layer is five pluggable backends, not one — and only two of the five have a shipped implementation you could put in a bucket.
Kopia — Profile
Its snapshot manifest has the free-text Description field restic lacks, and its policies attach per directory and inherit — the ask's own shape, in the store.
Rclone UI — Profile
The only entry that solves the trigger problem — 5,167 lines of Rust registering jobs with launchd, crontab, and Task Scheduler behind one trait.
restic — Profile
Its on-disk layout is data/<ab>/<sha256> plus snapshots/<id> — which is corpora-builder's unbuilt Phase 4, already shipped and hardened since 2014.
Seafile — Profile
Git's object model with content-defined chunking underneath and a human-readable description on every commit — and the S3 backend is the paid tier.
Syncthing — Profile
Closes a question two Lossless docs left open: a receive-only device does not silently orphan the collaborator's edit — it flags it, counts it, and offers Revert.
Ideas — the editor surface and the format
Fifteen ideas captured from a working session, sorted by what they would actually cost. Four are nearly free because the groundwork already shipped; two need work upstream in lfm before flave can touch them; one is already an open decision in the spec under a different name.
12-Factor Agents — Profile
Nothing to install — thirteen essays whose answer to "who owns the prompts, the context, the state, the control flow?" is always *you*.
5ire — Profile
5ire's MCP layer has no apply button — editing a server row in PGlite makes the client reconnect via the live-query changefeed.
Agent2Agent (A2A) Protocol — Profile
The load-bearing commitment isn't the JSON-RPC — it's *opacity*. An A2A agent publishes skills, never its prompts, memory, or tools.
Agent Harnesses — Answers to the Plan's Targeted Questions
Phase 2, not a survey: three questions — MCP tool scoping, trajectory logs, per-project config swaps — answered from the profiles.
AGENTS.md — Profile
The entire specification is one precedence rule: the closest `AGENTS.md` to the edited file wins. No schema, no validator.
Aider — Profile
Aider has no tool-call loop and no MCP client — not a thin one, none at all. It reads diffs straight out of plain chat text.