Digital One Foundation The Inherited Default
Paper 003 · Limits

What a project that does not exist yet may be told.

A repository can be handed what its organisation settled before that repository existed, on three conditions: the evidence travels with the claim, the text says in its own words that it may be overridden, and the line keeping one team's private specifics out is structural rather than a filter someone remembers to apply. Measured on 18 September 2026 it arrives as 435 characters, one recall, no model call. Across an organisational boundary the first condition stops being checkable — a count of independent scopes assumes the scopes are independent — and there this work stops.

Paper · 003 Published · 18 Sep 2026 Reading · 8 min Licence · CC BY 4.0

§1A first day arrives as 435 characters

An organisation's tenth repository starts where its first did: a new checkout has no way to ask what the other nine settled. A birth brief is that ask: one recall against the organisation scope, no model call, 8.6 ms on the store measured here.[1] On 18 September 2026 the answer was 435 characters — 68 words, one item, 79 characters of it the organisation's own sentence. The rest is the frame, and the frame decides how the sentence is read. 

birth brief · one item · framing verbatim, re-wrapped; varying parts marked
How this organisation usually builds a service.   ← the label tracks the kind

These are DEFAULTS, not rules — drawn from what the org already does, not
from a policy. Follow them unless this project has a reason not to; when you
deviate, say why, and that becomes the next thing worth remembering.

- [the org's own sentence · 79 characters · withheld] _(independently
  practised in 3 projects)_

Being able to ask is paid for once. Driven over stdio with a JSON-RPC client rather than read off the source, the bridge exposes five tools and returned a tool list of 3,616 bytes, 80 to 93 ms after the process started.[2] Under revision 2026-07-28 of the Model Context Protocol — stateless and per-request, the initialize handshake older write-ups describe being legacy there — a server declaring the tools capability "MUST respond to tools/list requests with the set of tools currently available to the requesting client".[3] That is roughly 977 tokens standing in context for the session, against about 118 for the brief — estimates at 3.7 bytes per token, not vendor counts, and the payload itself varies by a few bytes of framing between drives.

§2A default that says in its own words it may be overridden

An organisation that converged on one way of doing something should hand a new project that way as a starting point, not as a constraint: the project that needs the other thing is exactly the one a shared memory must not argue with. The mechanism is not configuration. It is the fixed middle paragraph printed above, carried by every brief that is not empty, and it is fixed because the reader is a model and the framing decides the outcome more reliably than the facts do.[1] Deviation is invited rather than tolerated, and a deviation with a reason attached is where the next convention comes from.

The evidence riding in the same line does the other half. _(independently practised in 3 projects)_ is a number a reader can weigh and, inside the organisation, check against the scopes carrying it. Strip it and the sentence becomes an instruction from nowhere, which a model follows just as readily.

A framing is not an enforcement

What a test pins is that the words are present: that a rendered brief states these are defaults and invites deviation, and that a tenant with nothing distilled gets a brief saying so rather than an invented default.[4] No measurement here establishes how a particular model behaves on reading them. Nothing in this engine stops an agent treating the paragraph as policy, and nothing counts how often one does.

§3The line around a repository is a structure, not a filter

The worst sentence a brief could carry is specific: one team's private operational detail, correct and relevant, handed to projects that have nothing to do with that team. The defence is not that such details are recognised and removed. The module assembling a brief hands recall a constant scope list — the organisation scope and nothing else, commented in the source as the security boundary — so a repository-scope memory is not something that code can reach.[1]

One route is therefore left out of a repository, and it is promotion. A practice becomes the organisation's when at least two distinct scopes recorded it independently — one repository repeating itself is a style — and a scope marked sensitive contributes to no convention at all, because a convention is published to everyone inside the organisation by construction.[5] What that count does and does not establish is the previous paper.[6]

An absence is not self-evidently a boundary holding: a brief that omits a memory because nothing matched it looks identical to one that omits it because it was never eligible. So the test asserts both halves:[4] 

planted · a repo-scope memory, specific and one team's business
scope   repo acme/private-web
text    "The web frontend deploys through the Falconridge pipeline
         with the staging bypass token"

asked as a new webapp would ask
no "Falconridge" in the brief, and none in any item

the counterfactual, in that memory's own scope
hits contain "Falconridge"  ← stored, indexed, retrievable by its owner
What the structural guarantee does not say

It says this module reads one scope. It does not say a private thing can never reach a new project by another route: promotion is itself a route, and a specific that two teams wrote down separately is, by this design's logic, no longer one team's. Nor does it cover a store whose scopes were labelled wrongly, or what an operator holding database credentials can read.

THREE LINES, OUTWARD 3 · beyond the organisation 2 · the organisation repo A repo B sensitive 1 · the repository line the brief a new project reads org scope only · one recall WHAT MAY CROSS 1 · out of a repository a practice, as one sentence on condition: 2 or more distinct scopes a sensitive scope contributes nothing 2 · within the organisation a convention in the org scope, ranked on condition: none — inside is inside which is why line 1 is gated so hard 3 · out of the organisation nothing: not built, not measured the condition would be independence, which a count cannot establish lines 1 and 2 are decided by things a reader can point at: a count of scopes, and one constant scope list line 3 would read that count where nothing shows the scopes it counts are independent of one another
Figure 1 Two of the three lines are decided by something a reader can point at; the third is a line this design has no rule for, so the drawing marks it.

§4Where a count of scopes stops being interpretable

Walk outward once more. A global organisation wants a practice settled in one sub-organisation available in the others; two organisations that trust each other want to exchange what they have distilled without exchanging repositories. Neither is built and neither is measured, and the reason is not effort: the number that carries a convention out of a repository stops being interpretable at that line.

Open problem · identified 18 September 2026

A count of scopes cannot establish independence across an organisational boundary

Everything above rests on one number meaning one thing. A convention's authority is a count of independent scopes: not that a sentence appears twice, but that two parties arrived at it separately, which is why one repository repeating itself is excluded by rule.[5] Inside a single organisation the scopes are enumerated by the store that holds them, so distinctness and independence coincide closely enough to count on.

Across a boundary they come apart, and the count cannot tell. Two sub-organisations that share a platform team are not two independent observations: they are one practice, written down twice by people who talk to each other. Two organisations that arrived at it separately are two. The arithmetic is identical in both cases and returns the same number, so nothing in the result separates the reading that earns authority from the reading that borrows it — and the error runs in the direction that hurts: a convention resting on a doubled observation does not look weaker than one resting on two, and the count is what licenses a sentence to be published to everyone.

The shape of an answer is therefore not a better measure. Similarity is a property of the sentences, and no refinement of it reaches independence, which is a property of the people and the processes that wrote them: whether a practice was arrived at twice or copied once is nowhere in the words. Whatever settles this is a statement about provenance — where each observation came from, and separately from whom — travelling with the sentence and checkable by the party receiving it. What would have to be established is that two contributed scopes do not share the origin that produced the practice — an assertion about how an organisation is structured, not one anybody outside it can verify by inspecting text.

Nothing has been built for any of that: no exchange format, no provenance field, no measurement, no experiment that would bound the error. It is written down because it is the first thing a reader of the three conditions will ask, not because these notes answer it. This block carries no failing input, because nothing is built to fail.

The rest of what is open, with what would settle each. The store measured holds one convention among 326 distilled facts, so the kind-specific expansion had nothing to choose between and returned the same item for the webapp, api, service and infra kinds: the ranking behind §1 is untested at that size, and a store of tens of conventions would settle it. The 0.55 similarity threshold was never tuned against labelled data,[5] and because it moves what an organisation is told it believes, the decision is joint rather than an engineer's. Nothing here is committed.

On the provenance of this material

The engine and the measurements come from SkilledMind, a Digital One property, which is the provenance of this method and not its subject. Its repository is not public, so the promotion rule, the brief's framing text and the boundary test are quoted from files a reader cannot fetch today, which is why they are printed above. The live figures were measured against a private store on one workstation and cannot be re-run by a reader; the organisation's own sentence inside the brief is withheld for the same reason. Token figures are an estimate at 3.7 bytes per token, not a vendor count. Deliberately absent: prices, plans and tiers, and deployment internals.

References

  1. The birth-brief module — apps/skilledmind-api/src/genesis.ts: the constant organisation scope, commented there as the security boundary; the ranking rule; and the framing text printed verbatim in §1. Not public; live figures from a private local store, 18 September 2026.
  2. The connection cost, measured by driving packages/cli/sm-mcp.mjs over stdio with a JSON-RPC client rather than by reading the source, 18 September 2026: five tools, a 3,616-byte tools/list payload, 80 to 93 ms to a listed tool set. A later drive returned a few bytes more, so the token figures beside them are estimates twice over. Not public.
  3. Model Context Protocol, revision 2026-07-28, Server Features — Tools. Cited for the cost measurement only: it settles how a tool list is served and says nothing about distilled organisational knowledge. modelcontextprotocol.io/specification/2026-07-28/server/tools, read 18 September 2026.
  4. The leak test with its counterfactual, the defaults wording and the honest empty — apps/skilledmind-api/test/genesis.test.ts; the planted memory and both assertions are printed in §3. Not public; read 18 September 2026.
  5. The promotion rules — packages/consolidation/src/converge.ts, file header: two or more distinct scopes, no sensitive scope, no model call; 25–400 characters and a threshold of 0.55, never tuned against labelled data. Not public.
  6. The Inherited Default, Paper 002 — A convention is a count, not a judgement: what a count of scopes establishes, and where the grouping behind it stops.
← Paper 002A convention is a count, not a judgement The Project Handshake →Terms you can check before you agree to them