Where the canon layer
goes next.

One schema per department.

Each department gets a grounding type: a schema that defines how its knowledge is structured into queryable canon. Message House is the flagship; Engineering Spec and Policy Shield are the proof that this is organizational infrastructure, not a PMM tool.

The flagship schema is documented at /message-house.

Canon you can govern, not just query.

The milestone that turns MsgStack into a governance layer: score any content against the canon, gate generation on approval status, and give every claim a named owner. Much of it has already landed ahead of the milestone.

• ✦Alignment scoring — per-section 0–100 reports with hard vs soft conflict classificationShipped
• ✦Approval-gated grounding — generation skips non-approved entries by defaultShipped
• ✦Content tiering — per-entry contract from Tier 1 verbatim to Tier 3 groundedShipped
• ✦DRI ownership — a named accountable person on every entry and domainShipped
• ✦Query audit log — every grounding query logged with caller, results, and latencyShipped
• ·Content SLA — per-domain review cadences with trigger events and breach alertsPlanned
• ·Dual output — citation-marked review copy alongside the clean deliverablePlanned
• ·Self-service portal — shareable generation link, no admin account requiredPlanned

Beyond marketing, into every domain of truth.

The proof that MsgStack is an organizational canon layer, not a PMM tool: grounding schemas for Engineering and Legal, dependency edges between domains, and a promotion pipeline that treats canon changes like code merges.

• ·engineering_spec grounding type — API constraints, SLAs, deprecation noticesPlanned
• ·policy_shield grounding type — legal language retrieved verbatim, never paraphrasedPlanned
• ✦Sub-canons — nested domains with four configurable inheritance policiesShipped
• ·Cross-domain dependency edges — INFORMS and DEPENDS_ON relationshipsPlanned
• ·Cascade drift detection — parent updates flag every downstream artifactPlanned
• ·Content CI/CD pipeline — validate, test, merge, propagate, auditPlanned
• ·Golden query datasets — retrieval benchmarks that gate promotionPlanned
• ·Identity-scoped retrieval — SSO login and per-user embargo scopingPlanned

More sources, sharper grounding.

Broaden what the canon can ingest — decks, spreadsheets, audio — and bring competitive intelligence into the graph so battlecards counter what competitors actually say.

• ✦PPTX and XLSX extractionShipped
• ✦Ingestion conflict detection — uploads flagged against existing canon before commitShipped
• ·Render-mode tagging — verbatim-insert vs parse-as-content per assetPlanned
• ·Industry and segment variants — persona × channel × industry retrievalPlanned
• ·Deck indexing and presentation assembly from approved slidesPlanned
• ·Audio and video indexing with timestamped moment retrievalPlanned
• ·Competitor document import and competitive gap analysisPlanned

From generated to published.

Close the gap between an approved artifact and a live asset: push grounded content into the systems where GTM teams already work, and pull published assets back in for alignment scoring.

• ·HubSpot — email drafts, social queue, and asset pull-back for scoringPlanned
• ·LinkedIn — publish social cards to company pages and profilesPlanned
• ·Salesforce — approved messages and battlecards as opportunity snippetsPlanned
• ·Google Docs export into a designated Drive folderPlanned
• ·Slack app — /msgstack generate, grounded content in the channelPlanned
• ·Outbound webhooks — send any artifact to any external systemPlanned

Agents over the canon, and a hosted edition.

Specialized agents for governance, voice, and structure sit over the pipeline, a conversation-first navigator answers questions about the canon — and a managed hosted edition opens MsgStack to teams that don't want to self-host.

• ✦Specialized agents — governance, brand voice, and narrative structure analysisShipped
• ✦Canon Navigator — conversation-first dashboard agent with streaming chatShipped
• ✦Tonal sliders and controlled vocabulary filters on generationShipped
• ·Hosted SaaS mode — managed database, index, and serverPlanned
• ·Onboarding wizard and industry starter templatesPlanned
• ·Recommendation routing — agents suggest where new material fits the canonPlanned
• ·Intent-based routing — the right model tier and skill chosen per queryPlanned
• ·Content analytics — usage heatmaps, acceptance signals, value reportingPlanned

The wider constellation, loosely charted.

Later milestones and the unscheduled backlog — source connectors, advanced graph operations, and platform ecosystem work. Sequencing here depends on community feedback more than anywhere else on the map.

• ✦Google Drive sync — OAuth connector and background sync loopShipped
• ·OneDrive, SharePoint, Notion, and Confluence connectorsPlanned
• ·Persona coverage analysis and cross-domain graph queriesPlanned
• ·Neo4j migration path for high-scale graphsPlanned
• ·Cross-domain search — one question across every department's canonPlanned
• ·Multi-LLM support — Claude, Gemini, and local models via OllamaPlanned
• ·CLI tool and VS Code extension for inline claim suggestionsPlanned