svc-asset-librarian — Configuration

DEV This is the dev environment. Changes saved here take effect immediately — there is no separate publish step. Local development · commit 0f46284 · Sign out

SharePoint

Site URL

Leave blank until the site exists. While it is blank this service cannot file to SharePoint, and says so on /health.

Drop library

Published library

Default retention (months)

Destinations — one row per classification

A destination is a permission boundary (AF-002). Classification alone chooses it; nothing else may. This service never grants or widens access — the library's permissions must already exist.

Classification

Destination id

Name

Library URL (optional)

Classification

Destination id

Name

Library URL (optional)

Classification

Destination id

Name

Library URL (optional)

Classification

Destination id

Name

Library URL (optional)

Filing rules

Taxonomy version

Scenarios — id, name, description, defaultClassification (the floor), keywords

[
  {
    "id": "SC-01",
    "name": "Internal explainer / walkthrough",
    "description": "How something works, recorded for staff.",
    "defaultClassification": "INTERNAL",
    "keywords": [
      "walkthrough",
      "explainer",
      "how it works",
      "internal",
      "demo of the process",
      "step by step",
      "overview of the system"
    ]
  },
  {
    "id": "SC-02",
    "name": "Onboarding and training",
    "description": "Repeatable instruction for new starters.",
    "defaultClassification": "INTERNAL",
    "keywords": [
      "onboarding",
      "training",
      "new starter",
      "induction",
      "getting started",
      "course",
      "your first week"
    ]
  },
  {
    "id": "SC-03",
    "name": "Leadership briefing",
    "description": "Strategy, performance and plans discussed by leadership.",
    "defaultClassification": "CONFIDENTIAL",
    "keywords": [
      "leadership",
      "board",
      "strategy",
      "strategic plan",
      "headcount",
      "roadmap for the year",
      "quarterly business review"
    ]
  },
  {
    "id": "SC-04",
    "name": "Commercial and financial review",
    "description": "Pricing, margin, forecast and cash.",
    "defaultClassification": "CONFIDENTIAL",
    "keywords": [
      "pricing",
      "margin",
      "forecast",
      "cash flow",
      "revenue",
      "invoice",
      "rate card",
      "budget"
    ]
  },
  {
    "id": "SC-05",
    "name": "Client-facing explainer",
    "description": "Intended for a client audience. INTERNAL until released; release terms are set per engagement by a human.",
    "defaultClassification": "INTERNAL",
    "keywords": [
      "for the client",
      "client audience",
      "hand over to the client",
      "engagement walkthrough",
      "client training"
    ]
  },
  {
    "id": "SC-06",
    "name": "Client engagement recording",
    "description": "Recorded with or about an engagement.",
    "defaultClassification": "RESTRICTED",
    "keywords": [
      "engagement",
      "workshop with the client",
      "requirements session",
      "matter",
      "steering committee",
      "client meeting"
    ]
  },
  {
    "id": "SC-07",
    "name": "Product / capability demonstration",
    "description": "Showing a product or capability.",
    "defaultClassification": "INTERNAL",
    "keywords": [
      "demonstration",
      "demo",
      "feature",
      "capability",
      "product tour",
      "release notes",
      "new version"
    ]
  },
  {
    "id": "SC-08",
    "name": "Incident or post-mortem",
    "description": "What broke and why.",
    "defaultClassification": "CONFIDENTIAL",
    "keywords": [
      "incident",
      "post-mortem",
      "postmortem",
      "outage",
      "root cause",
      "what went wrong",
      "remediation"
    ]
  },
  {
    "id": "SC-09",
    "name": "Marketing and external publication",
    "description": "Intended to leave the organisation. PUBLIC only after a named approval, which an automated proposal cannot give — the seeded floor stays INTERNAL.",
    "defaultClassification": "INTERNAL",
    "keywords": [
      "marketing",
      "campaign",
      "publish externally",
      "press",
      "webinar",
      "public launch",
      "social media"
    ]
  },
  {
    "id": "SC-99",
    "name": "No conclusion",
    "description": "The transcript supports no scenario above. Held for review at the highest configured default (AF-003, AF-007).",
    "defaultClassification": "RESTRICTED",
    "keywords": []
  }
]

A floor may be RAISED and never lowered, and a seeded scenario may never be removed. An attempt is refused by name rather than quietly applied.

Exception rules — id, name, when, then

Applied in order, last match wins per property. A rule that tries to lower a classification is recorded and refused, never honoured.

Who may change this

Keystone role granting admin

Administrator allowlist (one email per line)

Keystone app roles are not yet assigned for this app, so the allowlist is what currently carries the permission. Whichever grants, reads need only a session; writes need one of these two.

Why are you making this change?

I understand this changes live filing policy for DEV immediately.

Tick the confirmation to enable saving.

Change history

Revision	Changed by	When	Note
1	system:seed	2026-08-13T12:23:34.064Z