First Class Modules

OpsAtlas operating memory

Shows Knowledge Core health, answers operating questions from authorized published evidence, captures unsupported questions as gaps, and queues approved records for multimodal indexing.

Use the OpsAtlas renderer beside the native Knowledge Core lifecycle when employees need current, role-aware guidance with exact source and visual evidence.

What it does

Shows Knowledge Core health, answers operating questions from authorized published evidence, captures unsupported questions as gaps, and queues approved records for multimodal indexing.

Key capabilities

• Show published, review-due, and gap health from the secured Knowledge Core.
• Return bounded cited answers from current authorized evidence.
• Preserve page, element, source-record, and visual references.
• Capture unsupported questions through the native Knowledge Question workflow instead of guessing.
• Queue only already-visible and AI-readable records for durable indexing.

Common uses

• Operating-procedure lookup.
• Employee onboarding and policy guidance.
• Knowledge-gap capture and accountable curation.
• Governed agent instruction retrieval.

How it connects

The renderer uses native Knowledge Core items, immutable revisions, owners, reviews, questions, gaps, files, favorites, relations, and activity plus the canonical multimodal AI pipeline.

Where applicable, its records use the universal RecordId conventions so they can participate in secured relationships, activity history, favorites, dynamic fields, notifications, Inbox attention, and global search without copying the source record.

Security and data boundary

Only Published, deliberately AI-eligible material within the represented user's tenant, DataRole, location, field, record, and CanAiReadRecords envelope can become answer context. Material actions remain separately authorized and approval governed.

• The authenticated service derives the SaaS app, tenant account, user, DataRole, and location scope; browser identifiers are never authorization proof.
• The page editor composes React components with validated data bindings. Those bindings call typed runtime APIs, whose application services execute reviewed stored procedures.
• List, search, detail, relation, activity, favorite, and write operations reapply their required server-side permissions.

Add it to an app

1. Materialize the reviewed OpsAtlas production solution into an owned disposable or provisioned SaaS.
2. Add the validated module.ops-atlas block and native module.knowledge-articles block to the appropriate pages.
3. Assign Knowledge Core permission keys, owners, DataRoles, locations, and AI-read policy, then test draft exclusion, stale revisions, denied evidence, unsupported questions, and cited visual answers.