Builders
SDKs, schemas, examples, sandbox
Architecture overview
One canonical root. Many projections.
KYE Protocol™ organises every page, schema, profile, engine, rail, and surface under three macro groups: Protocol, Solutions, and Governance. One content graph projects into audience hubs, kind rails, and eight public surfaces, so a developer or an auditor finds the same canonical wherever they enter — the root is one; the views over it are many.
The cascade
From three macros to every page on the site
Each macro carries a semantic colour role (Protocol = accent, Solutions = info, Governance = success) declared in the canonical colour binding. The same role flows through chrome, page accents, and the diagram below.
Protocol The runtime, schemas, SDKs, ontology, profiles, and the spec itself.Solutions Sector products, consultants, partners, the buying audience.Governance Self-governance, evidence, attestations, frameworks, audit.
projects to
Partners
Consultants, trainers, distributors
General
Sectors, press, overview
CISO / CFO
Executive buyers, procurement
Counsel
Auditors, regulators, legal
renders through
landing sector framework library reference form demo
shipped on
site
marketing
app
tenant
admin
owners
dev
SDK
sandbox
demo
status
live
oss
standard
widgets
embed
Why one root
Every projection derives from the same content graph.
One root means one place to fix a fact: change the graph, and every surface that shows it re-derives at the next build.
The macro pills in the top bar, the audience hubs in the drawer, the footer rails, the breadcrumbs, the related links, the sitemap, the Cmd-K palette — none of them are hand-curated. Each one is a query over the canonical page graph, derived at build time. When a new page lands with its kye-audience, kye-stage, kye-kind, and kye-tier1-group meta tags, every surface that touches it updates in lockstep.
This is the founding organising principle: one canonical root, many projections. Discoverability never drifts from the source of truth. The top menu cannot disagree with the footer rails, the breadcrumbs cannot disagree with the parent graph, the search index cannot disagree with the page registry. They cannot disagree because they are all reads of the same single store.
Canonical KYE™ surfaces referenced on this page: KYE Protocol™.