Enterprise
Enterprise — what an organisation registers, what it keeps, and what it can show.
An organisation that is putting knowledge into machines has three problems at once: it does not know what it holds, it cannot say what its systems are licensed to use, and it is being asked to hand material to somebody else in order to find out. This page says what the register offers against each of those, in the register's own words, and what it refuses to offer at all.
This page answers the path I need to govern knowledge — Know what your systems are allowed to know.
Everything here is written as a design. No arrangement below is described as something that has run, and no figure, price or customer appears anywhere on this page.
Five things are offered to an organisation, and each one is a record rather than a service that touches your material.
A private register — a tenant of the Tacit Tessera register, with real numbers, sealed Cards and closed Book entries. Custody kept by the holder, with the local copy as the default. On-premise operation, where the work of converting and registering runs inside your own estate. The knowledge estate — what your organisation holds, recorded number by number. And the Knowledge Bill of Materials — the list of the numbers and editions a system is licensed to use. A bill of materials lists what was licensed, not what a model contains.
Beside those sit two things a company may do on the register rather than receive from it: administer its own rights, and register material the register did not capture. Both are in sections 07 and 08, and both stop at the same line — a person's paper is not a company's to hold.
Why this reads like a manufacturer's problem. Physical manufacturing reads a supply chain: supplier, component, assembly, product, customer. This is the same shape for knowledge — where it came from, what was made of it, what number it carries, what licence covers it, what was made from that, and what was counted. An organisation that can already answer those six questions about a bracket is being asked to answer them about the way its best people work, and it has no register in which to do it.
Everything below is one of those six links, taken properly.
A private register is a tenant of the Tacit Tessera register: real numbers, sealed Cards, closed Book entries.
What it is. One register issues numbers, and a private register is a tenant inside it rather than a copy of it. An entry registered privately gets a real number in the ordinary grammar, a Card sealed the ordinary way, and an event history kept the ordinary way. What is private is the Book entry: the entry's existence is not published, and it is carried in your tenant's closed Book entry.
Why it exists in this register. Most of what an organisation holds cannot be published and should not be. A method that took thirty years to settle, a procedure that is the difference between two competitors, a practice's own files — none of those can go on a public index, and the usual answer is that they stay unregistered, which means they stay unaddressed, unlicensed, uncounted and eventually unattributed. A private register is the answer to that: the discipline of a register without the publication of one.
What it records. Exactly what a published entry records — the number, the edition, the seal, the Card's five groups, the rights state, the consents, the conditions and the event history. Nothing is thinner because it is private. The difference is one field: how the entry is carried.
How an entry is carried, and it is not a ladder. An entry is carried in one of three ways: published, where the Book entry is public; restricted, where the entry is public and named fields are held licensee-side by the terms of registration; and closed, where the existence is not published and the entry sits in a private tenant's closed Book entry. These say where an entry is carried, not what a skill set is worth. There is no tier above another, nothing is upgraded, and the one public status word on this register is Specified.
What it refuses. A private register is never a second numbering scheme, and there is no such thing as a number that works only inside it — a number not in the registry is not a Tacit Tessera number. It never takes a customer's name in front of the bare word; it is the Tacit Tessera register, private tenant, and nothing else. And privacy does not reach the number: what is private is the Book entry, never the identity of the entry itself, because an address that only some parties can resolve is not an address.
The three readers. For the person in the seat, a closed entry changes nothing about their own side: the consents are still four, still separate, and still theirs to end. For a procurement officer it is the arrangement that lets a supplier's method be named in a contract without being published in one. For counsel, confidential registration raises its own questions — what changes for custody, for a coded contributor and for a challenge brought by somebody who cannot see the entry — and those are with counsel rather than answered here.
Registering a skill set does not require giving up custody of the material it was made from.
What it is. Custody is the plain question of who holds the readable copy. The material a skill set is made from — the recorded sessions, the converted paper, the files a practice worked from — stays where it is. What the register holds is the record: the number, the Card, the seal, the rights and the history.
Why the local copy is the default, not an upgrade. Because an arrangement that is only available on better terms is not a principle, it is a price. If keeping your own material were something you bought, then every organisation that did not buy it would have handed its material over as the ordinary case, and the ordinary case is the one that decides what a register actually is. The converter runs locally and the own copy does not leave; that is the default, and it does not have a tier above it.
What custody does not mean. It is not a claim that your material is safe, and this register makes none. It is not sovereignty over knowledge, which is a slogan rather than a mechanism. It does not mean the register cannot be asked questions about an entry — it can, and section 02 says which. And it does not travel to a third party: material a third party holds is that party's custody by the same definition, whatever the paper between you says.
What it records. Where the readable material sits is a fact about your estate, not a field on a public Card. What the Card records is what the entry was built from, in the register's words, and where the entry stops.
The three readers. For the person in the seat, custody is why a record of them working does not become somebody's library. For a procurement officer it is the answer to the first question an information-security review asks. For counsel it is the question underneath section 04, and that one is open.
The work runs where the material already is.
On-premise means what it says: the conversion and the registration run inside your own estate, against material that does not move. What leaves is the record — the number, the Card, the seal and the events — and what stays is everything the record is about.
This is the same arrangement custody describes, seen from the operating side rather than the legal one. It exists because the two ordinary alternatives are both worse: either the material is uploaded, which is the thing section 03 refuses, or nothing is registered at all, which is where most organisations are today.
What it refuses. It is not a claim about security controls, and this page names none. It is not a separate product with its own terms on top of registration. And it does not change what a Card says: an entry registered on-premise reads exactly as an entry registered any other way, because a register whose entries mean different things depending on where they were made is not a register.
Escrow is offered to an enterprise tenant knowingly, and what it costs is stated on the tenant's own paper.
The question, in one sentence. Where a tenant holds the readable copy and the register holds only a sealed one, is the register still responsible for the personal information inside it?
That it is open. No Canadian statute, decided case or regulator guidance answers it. The federal privacy statute pins responsibility in two places, in two different words — information in an organisation's possession or custody, and information under its control — and neither word is defined. The Commissioner's most recent guidance on third-party service providers repeats the possession-or-custody formulation. The direction of travel runs against the escrow theory, because accountability is pinned to custody rather than to readability. The legal position carries the instruments themselves, clause by clause.
What is built. Escrow is offered to an enterprise tenant knowingly, and what it costs is stated on the tenant's own paper. It moves the point of enforcement out of the register's hands — a permission written into a file is a label, not a lock, and enforcement lives where the reference is served. Three warranties are given up with it, and all three are named on the paper:
- The count That the ledger is append-only, its change types fixed, its history not rewritten.
- The stop on withdrawal That the register stops serving, records the stop, and keeps the withdrawal on file. It stops for new work at once; a job already underway finishes.
- The citations on a served passage That every answer carries its citations, because enforcement lives at the point of serving.
Counsel first, and nothing is built until counsel answers. No claim is made on this page or anywhere else that escrow is neutral, safe, in place or taken up by anyone, and the custody question above is left open rather than resolved in copy. A tenant that takes escrow is trading three things it could otherwise hold the register to, and it should know which three before it signs. The legal position writes every open question in this same three-step shape.
A knowledge estate is what an organisation holds, recorded number by number.
What it is. An estate is the whole of what an organisation holds, taken one entry at a time: what it is, who it came from, what may be done with it, and under what licence. Each line of it is a number, and each number resolves to a Card that answers those four questions in the register's own words rather than in a spreadsheet's.
Why it exists in this register. Because the alternative is a list of documents. A document list tells you a file exists; it does not tell you whose way of working is inside it, whether the person consented to it being held alongside others, whether a machine may run it, whether a model may be built from it, or what happens on the day the person says stop. Those are rights questions, and they are answerable only where rights are recorded against an identity that does not move.
What it records. For every entry: the number and edition; what the entry is and where it stops; the source and the house that collected it; the consents held and the conditions set; the licence kinds offered; how the entry is carried; and the event history. Read across the estate, that is an answer to what do we hold that survives the departure of the person who used to know.
What it refuses. No count of it appears on any page of this site. No valuation, no balance-sheet claim, and no product built on either — nothing here is a due-diligence report, a succession plan or an assessment of anybody, and none of those is described as having run. The estate is a record; what it is worth is a matter between parties on their own paper.
What happens when a source withdraws. An entry does not vanish from an estate; the licence to use it ends on the rule for its kind. It stops for new work at once; a job already underway finishes. For a learning or derivative licence, material used to build a model comes out at the model's next revision, and that date is stated to the person before they sign. The register never claims a model has forgotten anyone. An estate that records its numbers can answer, on the day, exactly which systems are affected; an estate that records filenames cannot.
The three readers. For the person in the seat, the estate is where their own number sits beside their name, never instead of it. For a procurement officer it is what turns a supplier's knowledge from a claim into a line item. For counsel it is the record a rights position is argued from, entry by entry, with the evidence filed against each one and the date it was filed.
A Knowledge Bill of Materials lists the numbers and editions a system is licensed to use.
A bill of materials lists what was licensed, not what a model contains. That sentence travels with the term every time it is written, and it is the reason the term is publishable at all.
What it is. One system — a model, an agent, a machine, a line of business software — and against it the list of entries it is licensed to use, each with its number, its edition, the licence kind, the conditions on it and the rights state as it stood when the licence was taken. It is the knowledge side of the document a manufacturer already produces for a physical assembly, and it is read the same way.
Why procurement asks for one. Because the question what is in this system has become an answerable question everywhere except knowledge. A buyer can ask what steel is in a frame and what libraries are in a build; it cannot, today, ask whose expertise is in a model and on what terms it got there. A bill of materials is the artefact that makes the question askable, and the register is the thing that makes the answer checkable: every line resolves to a number, every number resolves to a Card, and every Card's edition is sealed.
What it lists, line by line. The number. The edition. The licence kind — execution, learning or derivative. The conditions the contributor set, which travel on the Card and in the licence. The rights state. And, where an entry is a Set, the members recorded by number. Nothing else.
What it refuses, and this is the half that does the work. It carries no count and no quantity of anything. It carries no line saying a source was checked, because a check is something done to a seal rather than a rank a skill set holds. It is not a model card and it carries no measurements. And it makes no statement about what is inside the system it describes. What the register can show about a derived model is what was licensed for it, and nothing about what the model now contains. A bill of materials is a licensing record read forward from the paper, not an inventory read backward out of a model, and any reading of it as the second is a reading this register refuses.
The three readers. For the person in the seat it is where their number appears in somebody's system, with the edition pinned, so that a withdrawal has a list to act on. For a procurement officer it is the deliverable — the thing to ask a supplier for, and the thing to write into a specification. For counsel it is a record of permissions relied on, with its ceiling written into the same document so that it cannot be read as more than it is.
Asked for early, it is a list a supplier can produce. Asked for late, it is an audit nobody can finish, which is why it belongs in the specification rather than in the dispute.
A company may appoint someone to administer its rights on the register.
Where the holder of material is a company, somebody has to act for it — sign the registrations, answer the intake, set the conditions, hold the licences. A company may appoint a person to do that, and the register records who it is and what they are appointed to do.
A person's rights are administered by Even Steven and by nobody else. There is no appointment, arrangement, employment relationship or contract that puts a third party between a person and their own consents on this register. An employer may hold material and may hold rights in material; it never holds the person's side. A person's paper is always with Even Steven.
Steady Eddie and Strategic Agent require skill sets. Even Steven owns them. Tacit Tessera licenses them to OEMs and to AI. That separation is why the line in this section can be held: the house that holds the person's paper is not the house that licenses anything, and the register that licenses does not hold the person's consents.
What it refuses. No administrator is named on a page. No arrangement is described in which a person is represented by anyone but Even Steven. And no company is described as neutral as to the people its material came from — the intake asks, and the answer is recorded. Protect is written for the person and owns the four consents from their side; Even Steven is where every question about a person's own side goes.
The register may record material it did not capture.
Not everything worth registering was recorded by one of the houses. An OEM's manuals, a publisher's library, an association's or a university's collection — a body of material may already exist, held by an organisation that can say something about where it came from. The register may record it, and the intake establishes what the holder can assert about it.
What the intake must establish. Who made the material and in what relationship. What the holder's rights in it actually are, and on what instrument — assignment, employment, commission, licence or custom. Whether a person's own way of working is inside it and, if so, what they consented to. What third-party documents, confidential information or customer information it carries. What an existing contract restricts. And what evidence the holder can produce for each of those answers.
What the register does with the answers. It records them. It records who asserted them, on what date, and what evidence was produced with them. And it records that it has not tested the assertion. It does not decide who owns anything: a question of title between an employer and a person, or between a contractor and a customer, is decided where such questions are decided, and this register's record is evidence in it and nothing more.
The intake ends in one of four outcomes — clear, requires a release, private only, or cannot register — and the third of those is the one an organisation with a real library should expect to see often. Rights owns the intake and takes the four outcomes one at a time; Bring your records is the same intake written for the holder.
The refusals, named, because each one is a thing an enterprise buyer will otherwise assume.
Refused
What no enterprise arrangement on this register produces.
- No assessment of a person. A record is never supplied to assess the person, to an insurer or to anyone else. Not for hiring, not for review, not for underwriting, not for indemnity, and not on any track.
- No count, and no valuation. No number of entries, contributors, tenants, licences or hours appears on this site, and no worth is put on an estate here.
- No price. No rate, no tier, and no statement that anything is without charge — a statement about price is a price.
- No named customer. No tenant, buyer or organisation is named on this site, in either direction.
- No claim about a model's contents. A bill of materials lists what was licensed, and the register never claims a model has forgotten anyone.
- No settlement between parties. The register records what was licensed and what was counted; money moves on the parties' own paper, and the register never sits between them.
- No security claim. Records are sealed, appended and never rewritten. No control, audit, framework or attestation is named on this page, because naming one would be a claim about a thing rather than a description of a mechanism.
Each of those is refused in every form and however the question is put, because that is what it takes for a refusal to survive a procurement process.
What is left after the refusals is the offering: a record of what you hold, kept under numbers that do not move, with your material where it already is, and a list your systems can be held to. That is a smaller thing than an enterprise knowledge platform, and it is the part that is true.