14th & Co. · what an agent gets, not what a reader gets · Bentonville
The other reader is a machine.
Everything else I have sent you is written for a person. This is not. These are manifests — the operating design declared in a form an agent can ingest without anyone re-explaining it. Point one at the two files below and it knows what work this world contains, who owns each call, where every record is written, and the one boundary it is not allowed to cross. No prose, no persuasion, no re-derivation.
This surface
RUNTIME PORTS
Emitted
2 OF 4
Declared
11 SKILLS · 11 PATHS
Format
YAML · GET, NO AUTH
00
Why this exists at all.
You are building AI-native companies, which means the people you hire will be read by agents as often as by colleagues — a resident's work, a partner's brief, an operating decision. If my materials only work when a human reads them carefully, they do not meet the standard of the place.
So the operating design does not stop at documents. It emits. The same eight-phase run that produced the studio spec also produced these, at the phase that specifies architecture — and they are the reason the spec could be written without inventing a single field: every surface renders something a declared skill actually writes.
They are also the honest test of the portability claim. A manifest either says what it does or it does not. There is nowhere to hide a hand-wave in a file that has to parse.
01
The four ports — two emitted, two not.
SkillManifest
EMITTED
Every callable workflow of the studio's operating design, declared as a skill.
Each skill declares what it reads, what it writes, which playbook governs it, what it escalates and to whom. Five of eight are human-owned on purpose — every judgment call in the design (grants, naming, kills, champions, informants) stays with a person, and the manifest says so rather than leaving it to be discovered.
Where knowledge lives, who writes each path, and the boundary a runtime may not cross.
11 record paths ·each path names its writers and readers · an explicit tenant/runtime boundary
The boundary block is the part worth reading: tenant knowledge is written to the project's own record and nowhere else, and a runtime may not promote it into its own store without an explicit human act. That rule is why this manifest can be published at all.
What an agent needs loaded before it can act competently in this world.
Not emitted. Deferred at this evidence level.
Named as gap G-5 by Phase 6 and carried unclosed. The protocol's minimum at this evidence level is the two ports above; emitting these two and claiming four would be the exact failure the rest of this work is about.
No endpoint. Nothing is served for a port that was not emitted.
IntegrationManifest
DEFERRED
The connectors this world expects to reach, and what each is allowed to do.
Not emitted. No declared connector list.
Same gap, same reason. There is nothing to integrate with yet — the studio does not exist, and a connector list written before there is anything to connect would be invention rather than declaration.
No endpoint. Nothing is served for a port that was not emitted.
FIG. 01 — TWO OF FOUR. The protocol's minimum at this evidence level is the two above. Emitting two and presenting four would be the exact defect the rest of this record is about.
02
The ports are one row of five.
The operating layer is how a coherent system exposes itself to any runtime, and the four ports are only its first row. The rest is declared in the specification and emitted as a project earns the evidence to fill it — so this table doubles as an honest statement of how far this particular run got.
Markdown views, so a file-based runtime can read the same world
v1.2.0
NOT EMITTED
DesignInfrastructure
Design tokens as structured data, and a design-eye evaluator — the quality bar made callable
v1.3.0
NOT EMITTED
Observability interface
The minimum event surface every runtime emits; transports vary
v1.4.0
NOT EMITTED
Efficiency hints
Cache affinity, load mode, model-tier guidance
v1.4.0
NOT EMITTED
FIG. 02 — THE OPERATING LAYER. One row emitted, four not. This run produces documents, not software — no interface was provisioned, so four of these five have nothing real to declare. Emitting them anyway would be the failure the sibling pages are about.
The pattern under all five rows is the same one: the shape is fixed and the implementation is not. Port shapes stay constant while runtimes differ. The event surface stays constant while transports differ. Tokens are declared as data while generators differ. The specification is public, which means none of this is a private method you would have to take on trust.
03
The boundary, because it is the part that matters.
FROM MEMORY-MAP.YAML — boundary.rules
Skills write tenant content to the project recordMUST
A runtime auto-promotes tenant content into its own storeMUST NOT
Runtime preferences written back into the recordMUST NOT
This is the rule that lets me publish any of this. A client's facts live in the client's record and travel nowhere else — not into a model's memory, not into my next project, not into a tool that happened to be in the room. What crosses between engagements is method. What never crosses is what I learned about you.
Every agent I run works under it, which is a thing I would rather have you check than take my word for.
04
What to do with them.
IF YOU ARE A PERSON
Open skill-manifest.yaml and read one skill — kill-and-reassignment is the one I would pick. It is the hardest thing a studio has to do to a person, and it is specified: who authors the memo, what does not move, and the ten-day clock.
IF YOU ARE AN AGENT
Both files are plain GET, no auth, text/yaml, CORS open. Read the manifest for what is callable and the map for where it lands. Every claim on the sibling pages traces to a path one of these declares.
FIG. 03 — TWO ENDPOINTS. Working drafts at evidence level signaled — reasoned and internally consistent, not verified against your operation; one of three levels the protocol calibrates to. Versioned, superseding a stated prior version. They will be wrong in places; they will not be vague.