Skip to main content
The Publication Fabric

Know once. Govern once. Publish appropriately everywhere.

Organizations recreate the same knowledge again and again — for the board, the website, the sales deck, the investor update. Every copy drifts, goes stale, and loses the evidence behind it.

ArchitectureThe canon, rights and audience rendering are implemented. The full fabric is direction.
The problem

One fact. Eleven copies. Eleven versions of the truth.

Each audience gets its own hand-made version. By the time the fact changes, nobody knows which copies to fix — or which one was right.

  • Executivesv1
  • Employeesv2
  • Customersv3
  • Partnersv4
  • Investorsv1
  • Boardsv2
  • Governmentv3
  • Websitesv4
  • Reportsv1
  • Presentationsv2
  • Dashboardsv3
The fabric

From sources to every channel, through one canon.

Select a stage. Knowledge is established once, with its evidence and rights, then rendered for each channel rather than rewritten for it.

    • WebsiteIn development
    • Executive briefImplemented
    • Board viewImplemented
    • Customer portalIn development
    • Investor viewImplemented
    • Government viewConcept
    • AgentIn development
    • APIArchitecture
    • ReportImplemented

Stage 4 of 6

Canonical knowledge

One versioned knowledge object per fact, decision or capability — referenced, never copied.

Each channel does not own a copy. It renders a view of the same canonical object, so correcting the canon corrects every channel.

One object, many views

A new industrial opportunity enters Atlas.

Switch audiences. The words, emphasis and detail change for each. The identity, provenance, permissions, confidence and freshness do not.

Canonical knowledge object

Turbine monitoring retrofit at a provincial hydro utility

Illustrative

Today View

A retrofit program worth pursuing this quarter.

Fits two of our three strategic priorities. The window opens with a pre-notice expected next month. Recommendation: assign an owner and brief the board.

Included

  • Strategic fit
  • Timing
  • Recommendation
  • Private call notes

Withheld for this audience

Nothing — this audience sees the full object.

Preserved in every view

  • Canonical identity

    ko:opp/hydro-retrofit-7f3a · v4

  • Provenance

    3 of 3 sources visible to this audience

  • Permissions

    Internal — full evidence

  • Confidence

    Moderate — 3 corroborating sources

  • Freshness

    Updated 2 days ago

A content system

  • Stores pages that people write.
  • Each channel is its own copy.
  • Permissions apply to pages, not facts.
  • Provenance ends at the author.
  • Staleness is discovered by readers.

The Publication Fabric

  • Governs knowledge; pages are renderings.
  • Every channel references one canon.
  • Permissions apply to each fact and its evidence.
  • Provenance runs back to the source record.
  • Freshness is known, and changes propagate.

This is infrastructure for how an organization knows things — not a place to put its pages.

Implemented vs. direction

What exists today.

Much of the substrate already runs in Atlas. The fabric that reaches every channel is where it is heading.

  • Knowledge Kernel

    Versioned knowledge objects, typed relationships and evidence. Documents are assembled from references, never copies.

    Implemented
  • Provenance & rights engine

    Most-restrictive-wins rights and audience-ceiling redaction, enforced server-side.

    Implemented
  • Audience-scoped views

    Board, investor and executive views rendered from the same records. The Atlas overview itself is assembled this way.

    Implemented
  • Living documentation

    Operating documentation rendered live from the kernel, with AI-maintained freshness checks.

    Implemented
  • Customer portals and agent channels

    Governed views delivered to customers and to agents acting on the organization’s behalf.

    In development
  • The full Publication Fabric

    Every channel — including website, government and API — as a governed rendering of one canon.

    Architecture

How to read this page

Available today
Part of the commercial Atlas product customers can use now.
Implemented
Built in the platform and working, but not yet packaged as a product surface.
In development
Actively being built. Not available yet.
Architecture
Ratified design direction. The platform is being built toward it.
Concept
An idea this page explores. Not built and not committed.

Stop rewriting what your organization already knows.

Talk with us about establishing canonical knowledge once and publishing governed views to the audiences that need them.

The opportunity, audiences and channel views on this page are illustrative. Channels marked Architecture, In development or Concept are not available today.