Existence test
Every recurring word, heading, link, widget, control, badge, and mark must aid clarity, provide a material benefit, or relieve a material detriment. Otherwise remove it.
Canonical Knowledge-Action Object · 1.2.0
Nature repeats.
Design must too.
The patterns that govern beautiful thought and beautiful nature must also govern design: reduction, recursion, hierarchy, proportion, rhythm, relationship, and proof.
The test for every visible thing
Does it aid clarity or orientation?
Does it provide a material benefit?
Does it relieve a material detriment?
If every answer is no, remove it.
purpose
purpose
Reduction before addition
Repair incoherence by removing, grouping, deferring, or collapsing competition before adding form. Perfection is reductive.
nature
nature
Nature is the precedent
Use recurrence, hierarchy, proportion, fractal self-similarity, and rhythmic variation as structural constraints—not decorative references.
One recursive grammar
Apply the same law to the site, page, section, component, paragraph, image, interval, graph, admin surface, and source module.
system
system
One visual system
Use one shared type schema, palette, spacing scale, line-height system, heading grammar, component language, and contrast law across public, governance, graph, and admin surfaces.
Golden-ratio measure
Use proportional measures to govern width, scale, spacing, and recurrence. The ratio is an obligation on relationships, not an ornament.
orientation
orientation
Location before options
Expose the reader's current location, parent category, sibling family, and clear return path before presenting onward choices.
Hierarchy before volume
Fold complexity into the smallest useful categories and subcategories. Expand one relationship family at a time.
Sticky highest-level navigation
Keep a stable sticky header with only the highest-level human categories; place ontologies and subcategories inside intentional expanding hubs.
reading
reading
Editorial cadence
Repeat idea → development → image, visual, comparison, or proof → subheading. Do not allow more than two prose beats without a designed change in reading mode.
Invite reading
Keep line length, line spacing, heading scale, paragraph length, image rhythm, and contrast comfortable enough that reading feels inevitable rather than laborious.
Lists disclose logic
A list must become a category, sequence, comparison, map, or compact logic object. Never render walls of bullets, links, or raw pipe tables.
complexity
complexity
Collapse every optional layer
On every widget, default model commentary, provenance, machine procedures, raw fields, graph detail, controls, and secondary actions to a named collapsed disclosure.
Human surface first
Raw JSON and API resources must be explicitly labeled machine data and must never appear as ordinary primary navigation or accidental reader destinations.
interaction
interaction
Interaction must clarify
Search, filters, maps, AI interaction, and expandable ontologies must reduce uncertainty or reveal relationships. Interaction without comprehension is removed.
Relationship before click
Show why a link exists and what family it belongs to before asking a person to click it.
quality
quality
Content and design are inseparable
Unreadable design makes content unclear. Rendering must reject or repair malformed tables, link walls, contrast failures, and source structures before they reach readers.
Queryable and discoverable
Every reader surface requires categories, search or traversal, semantic headings, canonical metadata, structured data, valid internal links, and responsive behavior.
source
source
The inside is beautiful
Organize source as law → primitive → composition → surface → proof. Use shared names, one-directional dependencies, and no scattered local design inventions.
knowledge
knowledge
Article and Skill are one
An article explains a concept to a human. Its Skill directs model behavior. They share one identity, meaning, version, and provenance while using distinct language for distinct audiences.
Maximal interoperability
Article, Markdown, JSON, directory row, Skill, OIP contract, REST resource, graph node, conformance target, version, and receipt lineage are typed expressions of one identity. Shared identity does not require shared wording.
Failures become knowledge
Repeated model failures become negative-knowledge facets that can generate an article amendment, Skill instruction, conformance test, code repair, directory clarification, and regression proof.
Design ontology
Design includes the systems that make images and motion.
Open one family at a time. Each family binds its human meaning, model Skill, live directory contract, and official source documentation.
renders visual design withGPT Image2 contracts
renders visual design withGrok Image3 contracts
produces image and video design withArcAds4 contracts
api documentation sourceArcAds OpenAPI sourceArcAds / build source store ↗ARCADS GENERATEHuman articleModel SkillLive definition ARCADS VIDEO GENERATEHuman articleModel SkillLive definition ARCADS ROUTESHuman articleModel SkillLive definition ARCADS UPLOADHuman articleModel SkillLive definition
renders motion design withGrok Video2 contracts
One identity, many expressions
The article becomes a Skill.
The article explains to a human. The Skill tells a model how to act. The directory row exposes the live contract. OIP invokes it. Each expression uses the language its audience needs while preserving identity, meaning, version, relationships, and proof.
- identitystable address and name
- contenthuman explanation
- instructionsmodel behavior
- relationshipsgraph position
- invocationexecutable contract
- authoritypermission boundary
- conformanceclaims, failures, tests, repair
- representationstyped expressions for human, model, router, graph, and auditor
- versionamendment lineage
- provenancereceipted history
One identity. Many typed expressions. Each optimized for its audience and role.