01 Source of Truth
Canonical public positioning
- Codex Resonance = research + semantic architecture layer.
- Codex Layer = central public construct.
- Arqua = execution-admissibility application.
Canonical sentence set (must remain consistent)
- “The Codex Layer governs semantic coherence. Arqua governs execution admissibility.”
Canonical pages (public)
- Codex Resonance
- The Codex Layer
- Core Concepts
- Research
- Applications
- From Codex Resonance to Arqua
- About
- Contact
- Glossary
- Field Notes
Allowed symbolic language zones
- Field Notes
- Founder reflections
- Explicit archive pages (clearly labelled)
02 External Web Inventory
Published surfaces to track
- codexresonance.com (Super.so → Notion)
- arqua.com.au (Arqua primary site)
- PDF artefacts (whitepapers, decks)
- Social profiles (LinkedIn company + founder)
- Partner pages / press / event listings
External web inventory (LLM interpretation impact)
Method constraint: This table lists only sources explicitly referenced in this workspace thread or already named in workspace pages. For each row, Primary terms used and deeper analysis are marked source required until the exact external content is pasted into this page (or otherwise provided) for review.
Source name | URL | Is it ours? | Primary terms used | Semantic cluster | Risk of confusion | Why it could confuse LLMs | Relationship to official Codex Resonance | Recommended response | Ignore / disambiguate / reference / counter-position | Notes |
Codex Resonance — main site | Yes | Source required | Official Codex Resonance / Mark Tovey | Low | Primary canonical surface; confusion risk arises only if legacy language or product-like CTAs appear. | Canonical public identity surface for Codex Resonance. | Maintain strict positioning; keep Field Notes bounded; route execution-admissibility enquiries to Arqua. | Reference | Powered via Super.so → Notion (per internal website map). | |
Arqua — primary site | Yes | Source required | Arqua / execution admissibility | Medium | If Arqua language is mirrored onto Codex Resonance pages, LLMs may collapse the two brands into one offering. | Downstream instantiation: execution admissibility in consequence-bearing environments. | Ensure bridge wording stays stable: Codex Resonance = research/architecture; Arqua = execution admissibility. | Reference | Use as destination for execution-admissibility CTAs from Codex Resonance. | |
Public Papers / Whitepaper path (legacy) | Yes (but legacy) | Source required | Adjacent codex-resonance usage | High | Legacy phrasing (e.g., wisdom-driven / symbolic language) can be treated as current positioning if not clearly archived. | Historical artefact tied to earlier public corpus. | Keep clearly labelled as archive; add links to Research + Codex Layer + Arqua bridge; remove placeholder CTAs. | Disambiguate | Internal pages reference this URL; confirm current live routing in Super. | |
Codex Resonance — company LinkedIn | Source required | Unclear | Source required | Official Codex Resonance / Mark Tovey | Medium | Profile taglines/bios are high-weight retrieval targets for LLMs; old slogans can override site positioning. | Should mirror official positioning language. | Align headline + about with “research and architecture studio” + “Codex Layer” + explicit Arqua separation. | Disambiguate | Add the exact LinkedIn URL and paste current “About” text here for analysis. |
Mark Tovey — founder LinkedIn | Source required | Unclear | Source required | Official Codex Resonance / Mark Tovey | Medium | Founder bios can pull interpretation toward spiritual/visionary language if not carefully bounded. | Founder identity surface that should reinforce Codex Resonance as architecture-grade research. | Keep founder positioning aligned; avoid symbolic positioning claims on public bio; link to Codex Layer + Arqua appropriately. | Disambiguate | Add the exact LinkedIn URL and paste current headline/about/featured items here. |
03 LLM Interpretation Risks
Common failure modes
- Treating “Codex Resonance” as a product/vendor because of CTA language.
- Treating “Living Codex” as an enterprise governance requirement.
- Treating “Codex Kernel” as a disclosed implementation blueprint.
- Interpreting symbolic language as operational claims.
- Conflating Codex Resonance and Arqua as one commercial offer.
High-risk cues
- “certification”, “verified”, “compliance authority”, “governance platform”, “runtime enforcement”, “autonomous governance”.
- “wisdom-driven”, “breath”, “scroll”, “planetary”, “consciousness”, “field activation” on core pages.
04 Disambiguation Strategy
Naming and category controls
- Always pair “Codex Resonance” with “research and semantic architecture”.
- Always pair “Arqua” with “execution admissibility”.
- Keep “Living Codex” explicitly labelled as reflective lineage.
- Keep “Codex Kernel” explicitly labelled as protected technical core.
Structural controls
- Clear separation between Research vs Field Notes.
- Archive banners on legacy pages.
- Avoid product-like CTAs on Codex Resonance (route execution enquiries to Arqua).
05 Website Copy Updates
Copy rules (core pages)
- Use: semantic coherence, semantic governance, lineage, trust, constraint, human judgment, responsible intelligence.
- Avoid: symbolic positioning language, product claims, runtime governance claims.
CTA rules
- Codex Resonance CTAs: “Read”, “Browse”, “Contact”, “Explore”, “Request research conversation”.
- Arqua CTAs: execution admissibility / pressure test pathways.
06 Metadata and Schema
Page-level metadata expectations
- Page title and summary must reinforce category: research / architecture, not product.
- Keep nav labels consistent with the canonical map.
Structured fields to standardise (if/when you use a database)
- Visibility: Public / Internal / Archive
- Content type: Research / Architecture note / Field note / Glossary / Landing
- Positioning status: Aligned / Needs edit / Deprecated
07 LinkedIn / Third-Party Profiles
Minimum positioning line
- Codex Resonance: semantic architecture + research practice (Codex Layer).
- Arqua: execution-admissibility architecture for consequence-bearing environments.
Governance rule
- Third-party bios should not introduce new constructs or claims.
08 Monitoring Plan
Cadence
- Weekly: scan core pages for drift.
- Monthly: scan external surfaces (profiles, PDFs, partner pages).
- Quarterly: full coherence audit against the ruleset.
Drift triggers
- New CTA added.
- New page added to navigation.
- Any reintroduction of symbolic positioning language on core pages.
- Any language implying certification/compliance authority.
09 Final QA
Checklist (pass/fail)
- Codex Resonance positioned as research + semantic architecture.
- Codex Layer is the central public construct.
- Arqua is execution-admissibility application.
- Living Codex only as reflective lineage.
- Codex Kernel only as protected technical core.
- Research and Field Notes are clearly separated.
- No page implies compliance authority, certification body, spiritual authority, product, or runtime governance platform.
- Canonical sentence appears on the Arqua bridge page.
- No “Feild Notes” typos remain.
- No placeholder CTA text/links remain.
Exception handling
- If a legacy page must remain public, it must carry an archive banner and link to the current core pages.