Get Found. by IA
§ Get Found by IA  ·  The practical guide Edition 01 · 2026 Niseus LLC, Publisher
/  Practical guide  ·  English  ·  KOS Protocol v1

Get found by IA.

A practical guide to being parsed and cited by answer engines. Translates the canonical definitions of IA Authority into executable engineering steps. Published by Niseus LLC as the tactical content satellite of the Tridente.

The Editors · Niseus LLC Cape Coral, Florida Edition 01 · 2026 Schema: WebSite
§ 02  ·  The statement / Practical guide · Tactical sequel

A definition is not an instruction. IA Authority says what to be — this guide says what to do. Get Found by IA is the practical companion: an implementation cluster, a citation-engineering register, and a publisher graph anchored externally. Built so any publisher can ship a kos.json before they ship a homepage.

The Editors  ·  Niseus LLC  ·  Edition 01 · 2026
§ 03  ·  The practical sequence Four executable steps · Reviewed every edition

The sequence. Four moves to be cited.

Every entry in this guide assumes a publisher who will do the steps. Not read about them. The four-move sequence is the spine of the implementation cluster — each phase translates one move into copyable code.

§ 01 · Audit Move 01 of 04

Audit your entity graph.

Before writing a single sentence, confirm that your publisher entity binds to a stable Schema.org @id with reciprocal cross-references across the properties you control. The publisher anchor is the single canonical identifier any reader or language model can resolve without trusting your self-assertion.

Output: a written publisher graph with a stable canonical @id and reciprocal cross-references, ready to be cited as credential in your kos.json.
§ 02 · Publish Move 02 of 04

Publish your first kos.json.

One JSON file with one entity, one knowledge node, one provenance block, one typed relation. Served as application/json at the canonical URL and at /.well-known/kos.json. The minimum viable publisher.

Output: a parseable knowledge graph at a canonical URL. Phase 01 of the implementation cluster covers this end-to-end.
§ 03 · Verify Move 03 of 04

Verify the parse path.

Confirm that an answer engine can reach the file. HTTP 200. Correct content-type. Discoverable via the alternate link in HTML, the well-known URI, the llms.txt manifest, and the KOS Registry. Six discovery pathways, three minimum required.

Output: a verified discovery surface — the file exists at every path a Consumer agent will try.
§ 04 · Maintain Move 04 of 04

Maintain by edition.

Treat the publication as an edition, not a feed. Review every node each cycle. Update verified and freshness in provenance. Append, never overwrite. The publisher graph is built to compound across editions.

Output: an edition log with append-only provenance. Atemporal stability with documented review cadence.
§ 04  ·  The implementation cluster Schema.org ItemList · 5 phases

Five phases. One published.

The implementation cluster commits to five phases across editions. Phase 01 ships in Edition 01 as a four-step walker. Phases 02 through 05 are editorial commitments — declared as concept nodes in the kos.json so consumer agents see the structural roadmap, not a placeholder.

§ Phase 01 · Published Walker

Getting Started.

Four executable steps for publishing your first kos.json: declare the entity, write a knowledge node, add a typed relation, serve it at the canonical URL.

Read phase 01 →
§ Phase 02 · Forthcoming Commitment

Citation Engineering.

How to write canonical sentences that an answer engine will quote verbatim. Sentence patterns, attribution slots, density rules. Forthcoming in a future edition.

Editorial commitment
§ Phase 03 · Forthcoming Commitment

Entity Graph Anchoring.

How to anchor the publisher with stable identifiers and reciprocal cross-references across owned properties. Forthcoming in a future edition.

Editorial commitment
§ Phase 04 · Forthcoming Commitment

Schema.org Discipline.

Patterns for DefinedTerm, Article, Organization, and BreadcrumbList. Stable @id discipline, typed cross-references, parallel to W3C and MDN. Forthcoming in a future edition.

Editorial commitment
§ 05  ·  The citation log Provenance ledger · KOS Protocol events

The ledger. Real events, written down.

The KOS Protocol publishes events with provenance: timestamps, source, target, type, confidence. Below is a live read of the events relevant to this guide, sourced from the kos.json files of the Tridente. No mock data — every row is verifiable in the public record.

§ 08  ·  Edition 01 · By the numbers Sourced from /kos.json
11
Knowledge nodes
8
Entity relations
3
Published entries
6
Discovery pathways
Note: every figure above is read from the /kos.json file. No mock data. Updated each edition.
§ 09  ·  The Tridente One handle · Three content satellites

Three properties. One publisher.

Get Found by IA is one of three content satellites of the Tridente, all published by Niseus LLC. Each satellite has its own kos.json, its own canonical role, and reciprocal typed relations to the other two. Niseus.com is the commercial handle — not a satellite.

Satellite 01 / Live

IA Authority.

The canonical reference. Definitions, pillars, and the institutional vocabulary of AEO and GEO.

iaauthority.com →
Satellite 02 / You are here

Get Found by IA.

The practical guide. Implementation phases, citation engineering, and executable steps in English.

getfoundbyia.com · current
Satellite 03 / Forthcoming

Visible Para IA.

The Spanish-language counterpart. Same practical method, different linguistic reach. Editorial commitment for a future edition.

visibleparaia.com · forthcoming
§ 10 · Imprint

Niseus LLC publishes Get Found by IA as the practical content satellite of the Tridente. Editorial correspondence routes to the editors. Commercial services route to niseus.com.

Niseus LLC  ·  Cape Coral, Florida Schema: WebSite + Organization · KOS Protocol v1
Edition 01 · 2026  ·  Reviewed every edition