DocsBook a demo

Platform

Platform overviewArchitectureWorkflow orchestrationGitOps configurationGovernance and AAAAI and MCPKnowledge and contextRuntime and executionEvidence and monitoring

Use cases

All use casesProduction incidentRelease preparationHotfix to productionSecurity scan triage
Why NopsAIIntegrationsSecurity

Resources

All resourcesAI agent governanceMCP governanceMCP securitySelf-hosted platforms
PricingGitHub

Company

How a run worksAboutContactBook a demo

Knowledge Context

Documents injected into prompts, and the two kinds that can block execution outright.

ReferenceAutomation authorAdministratorSecurity

Key points

  • Supported kinds: architecture, guardrail, policy, adr, guideline, runbook, reference, example.
  • guardrail and policy are blocking kinds. They apply to goals, commands, direct scripts, file writes, MCP calls, MCP arguments, and conditions.
  • Use exactly one of ref (a managed team/document) or path (repo-local, loaded at the run commit).
  • A managed ref requires knowledge_context.use permission on that document.
  • required: true fails the run before execution when resolution or authorization fails.
  • Resolved content is snapshotted on the run, so later document edits never rewrite run history.
  • Documents, and the Notion/Confluence/wiki connections they attach to, are Git-owned: knowledge/connections/<team>/<connection>.yaml defines a connection, and a mirrored document declares source.type: external_page with the page reference and sync settings.
  • The mirrored page body, sync status, and cached content stay runtime state, so an upstream page edit is never reported as configuration drift.

Field reference

knowledge_context[].kindknowledge refstringRequiredNone

Document kind. guardrail and policy are blocking kinds that also validate direct scripts.

Example

kind: guardrail

Allowed values

architecture, guardrail, policy, adr, guideline, runbook, reference, example

Rules
  • Matching is case-insensitive; unsupported kinds fail validation.
Evidence

services/nopsai/pkg/validation/pipeline.go

knowledge_context[].refknowledge refstringConditionalNone

Managed document reference in team/document form.

Example

ref: security/repo-check

Rules
  • Exactly one of ref or path must be set.
  • Must be relative and contain at least two segments.
  • Segments may not be empty, ., or ...
Permission

Requires knowledge_context.use on the referenced document.

Evidence

services/nopsai/pkg/validation/pipeline.go

knowledge_context[].pathknowledge refstringConditionalNone

Repository-local document loaded from the run repository at the run commit.

Example

path: .nopsai/docs/backend.md

Rules
  • Exactly one of ref or path must be set.
  • Must be a relative path without . or .. segments.
Evidence

services/nopsai/pkg/validation/pipeline.go

knowledge_context[].requiredknowledge refbooleanOptionalfalse

When true, the run fails before execution if the document cannot be resolved or authorized.

Example

required: true

Security

Leaving this false lets a run proceed without a guardrail the author expected to be applied.

Examples

Managed guardrail plus a repo-local exampleyaml
knowledge_context:
  - kind: guardrail
    ref: security/repo-check
    required: true
  - kind: architecture
    path: .nopsai/docs/backend.md
Result

The guardrail must resolve and authorize or the run fails before execution. The architecture document is read from the run repository at the run commit.

How it works

Pipeline, step, and task knowledge context are merged, not replaced. The most specific level adds to what the broader levels already supply.

Blocking kinds are pinned by scope at run start and recomputed as pipeline, step, and task scopes begin. Emergency policy response cancels active runs rather than mutating already-resolved policy.

A script step with blocking context has its exact command LLM-validated before execution. That is why llm_enabled: false rejects such a combination.

Implementation evidence

  • services/nopsai/pkg/validation/pipeline.go

    Kind, ref, and path validation.

  • doc/knowledge-context.md

    GitOps layout, runtime snapshots, and access checks.