The practical sequel.

The canonical reference at IA Authority is a publication built on a single editorial choice: to write definitions that an answer engine can quote. Five pillar articles, twelve DefinedTerm entries, three editorial essays. Every entry has a stable @id, a provenance block, and an institutional byline. The reference is parseable by design.

And yet the canonical reference, by itself, leaves the publisher who wants to be cited in a strange position: they know what AEO is, and they still do not know what to do. They have read the definition. They have understood that answer engines compose answers from structured sources. They have agreed that the discipline is real. They are still staring at an empty homepage with no idea what to type first.

This is not a defect of the canonical reference. A canonical reference is supposed to be a noun, not a verb. The five-pillar cluster at IA Authority describes a discipline; it is not obligated to ship the engineering manual. Schema.org defines DefinedTerm; it does not write the for-loop that emits the JSON-LD. W3C publishes specifications; it does not run the implementer's CI/CD pipeline. The institutional publisher's job is to write the noun with discipline.

But there is a structural absence. Between the canonical reference and the publisher who wants to act on it, there should be a second publication: a practical guide that says, in order, what to write first, what to write second, what to verify before declaring a phase complete, and what to leave for the next edition. Get Found by IA is that second publication.

The thesis.

A practical guide is not the same as a how-to article. A how-to article tells one publisher how to solve one problem once. A practical guide is a publication with the same editorial discipline as the canonical reference, but with a different test for entry: every published phase must ship with executable code, every published term must name an engineering move, and every published essay must defend an editorial principle that informs the implementation cluster.

The editorial byline from IA Authority is preserved: The Editors at Niseus LLC as the publisher of record. The publisher graph binds every published claim to the stable Schema.org @id of Niseus LLC, with reciprocal sameAs across the Tridente content satellites.

What changes is the test of an entry. In a canonical reference, the test is whether the definition is precise. In a practical guide, the test is whether a publisher can act on the entry. A definition without a corresponding action belongs in the reference, not in the guide. An action without a corresponding definition belongs in the implementation cluster, with a cross-reference to the reference where the noun lives.

What gets shipped.

The practical register names twelve engineering moves, of which the first — citation engineering — is the editorial discipline of writing canonical sentences a machine can quote. The implementation cluster commits to five phases, of which the first is a four-step walker for publishing a first kos.json end-to-end. The editorial essays, of which this is the founding entry, defend the principles that govern the register and the cluster.

Every published page in the guide carries at least one executable artefact. Phase 01 ships four code blocks. The DefinedTerm for citation engineering ships a usage example. This essay ships a thesis sentence with a stable @id that the implementation cluster cross-references. The pattern is recursive: the publication that teaches publishers how to be cited is itself written to be cited.

What does not get shipped: opinion pieces about the AI industry, news about model releases, ranking benchmarks, performance studies, anything time-bound. Get Found by IA is built to be atemporal. Edition is the only time-bound layer. The four-step walker for publishing a first kos.json will not be obsolete in a future model generation, because the four steps describe a transport-level discipline (declare, write, bind, serve) that is independent of which language model happens to be popular when a publisher reads it.

The relationship to the canonical reference.

This guide does not replace the canonical reference. It depends on it. Every implementation phase carries a typed relation to a canonical pillar at IA Authority; every practical glossary entry carries a typed relation to a canonical DefinedTerm at IA Authority. The two publications are reciprocally cross-referenced through their kos.json files. A consumer agent that fetches one will find a path to the other.

The Tridente metaphor is precise: niseus.com is the handle, and the three content satellites — IA Authority, Get Found by IA, and Visible Para IA — are the three prongs. The handle holds the prongs together by anchoring the publisher graph commercially; the prongs each publish a different layer of the same canonical knowledge for a different reader and a different language. None of the three replaces the others.

The commitment.

Get Found by IA publishes the practical guide reviewed every edition, with executable artefacts on every page. The guide is anchored to the KOS Protocol as its spine. Every kos.json file the guide publishes will be cross-referenced reciprocally with the canonical reference and with the publisher's commercial handle.

That is the editorial method. A definition is not an instruction. The canonical reference says what to be — the practical guide says what to do. One without the other is half a publication.