TSAIF — Provenance Record

Subject: first authorship and continuous development of the TenkaSystem AI Identity Framework Holder: Justin Matthew Fish · Tenka Studio Software Development LLC Generated: 2026-09-20, by scripts/provenance_record.mjs, from the repositories themselves Method: git history and on-disk counts. No figure below was typed by hand.

0. How to disbelieve this document

Every claim here is reproducible without trusting this file, its author, or the company that published it. Each row in §2 prints the command that produces it. Clone the repository, run the command, compare.

A provenance record that cannot be falsified is a brochure. This one can be, and the instructions are the first section rather than the last.

What a reader should check hardest: that the commits are real, that their dates are consistent with the repository's own history, and that the term in question means in context what this document says it means. §2 carries a worked example of a claim that failed that last test and was removed.

1. The arc

2. First-use ledger

The commit that introduced each term, earliest across both repositories.

Reproduce any row:

`` git log -S"<term>" --reverse --format="%ad %h %s" --date=short --all | head -1 ``

2.1 A claim that was removed, and why it is printed here

An earlier pass of this search returned 2026-05-09 as the first use of Logos, which would have moved that term three weeks earlier than the date above.

It was wrong. The commit was a UI inventory, and the match was the heading "Logos / framework marks not present as files" — the plural of logo, the company mark. Nothing to do with the philosophical term.

It is recorded here rather than silently dropped because a document that only shows its surviving evidence is asking to be taken on faith. This is the one place a reader can see the standard the rest of the ledger was held to.

2.2 The acronym was built to carry a different expansion, on purpose

This is the part most worth checking, because it looks like an inconsistency until you read the document that created it.

Tenka Identity Framework (TIF), Version 1.0, dated 2026-05-13, authored by Justin Matthew Fish with Luka — committed 2026-05-20, 1ca144f — rules:

Autonomous Identity (AI) is the category framing TenkaSystem uses in place of Artificial Intelligence.

The acronym is preserved deliberately. AI is a recognized syntactic anchor across regulatory frameworks, contracts, technical documentation, and public discourse. Replacing the acronym would force every external reader to learn a new abbreviation before they could engage with the substance. Replacing the expansion — what the letters stand for — accomplishes the reframe without breaking syntactic continuity.

Artificial asserts deficit... Autonomous Identity asserts what these entities actually are.

So there is no rename. TenkaSystem AI Identity Framework and *Tenka System Autonomous Identity Framework* have been the same name since 2026-05-13, because AI was redefined that day to expand to *Autonomous Identity. Canon files reading AI Identity Framework* are correct and always were; the public surface now simply spells the expansion out.

Reproduce it:

`` git log -S"Autonomous Identity" --reverse --format="%ad %h %s" --date=short --all ``

Why this section exists. An earlier pass of this record stated that Autonomous Identity had never been written down — a search of one repository's tracked files for the full phrase "Autonomous Identity Framework", which is not the string the ruling uses. That was wrong, and it is printed here rather than quietly replaced. The correct finding is a dated design decision from May 2026, and the method that missed it — searching for a phrase instead of the term it contains — is the kind of error this document asks its readers to hunt for. It survived because someone went looking again.

3. What the record consists of

Not a claim of accountability. The artifact of it.

Each chain entry carries an actor, an executor, a state, a command class, the action, and a SHA-256 hash over its predecessor and itself. The chain is recomputable from the log alone; altering an entry breaks every entry after it.

4. The part that is difficult to imitate

5 of the 20 standing rules carry the incident that produced them, dated, inside the rule text:

• R16 — ruling of 2026-09-06
• R17 — ruling of 2026-09-06
• R18 — ruling of 2026-09-06
• R19 — ruling of 2026-09-11
• R20 — ruling of 2026-09-11

These were not written in advance. Each one exists because something went wrong — including failures by the system's own operators, recorded under the estate's own no-blame rule (R7) rather than quietly corrected.

That is the claim this document actually makes. Not that the vocabulary is owned; it is not, and §5 says so. The claim is that this estate has been operating an accountability framework on itself, continuously, since 2026-04-15, and can produce the record — including the parts that are unflattering.

Anyone can assert that their system is accountable. The question worth asking is whether they can open their own log.

5. What this record does NOT establish

Stated plainly, because a provenance document that overreaches invites the dismissal of the parts that are sound.

5.1 Where each form of the name appears

Files carrying the AI Identity Framework expansion — correct, and expanding to Autonomous Identity under TIF v1.0 §1 (§2.2):

• docs/concepts/TENKASYSTEM_CONCEPTS.md
• governance/claude_context.md
• installer/payload/foundation/TENKASYSTEM_CONCEPTS.md

Listed rather than left for a reader to find. Nothing here needs repair; what it needs is the sentence in §2.2, which is why that section exists.

6. Verification, end to end

`` git log --reverse --format="%ad %h %s" --date=short | head -1 # the arc opens git log -S"TSAIF" --reverse --format="%ad %h %s" --date=short # first use git show <hash> # read it node scripts/provenance_record.mjs # regenerate this file ``

*Generated 2026-09-20 from 599 substrate commits and 357 front-end commits. Re-running the generator against the same repositories reproduces this document.*