{
  "schemaVersion": 1,
  "publishedAt": "2026-10-16",
  "baseUrl": "https://docs.signalscorps.com",
  "topics": [
    {
      "id": "platform.workspaces",
      "title": "Workspaces",
      "summary": "A Workspace is the complete customer boundary for people, billing, connections, policy, repositories, scans, findings, and entitlements.",
      "path": "/overview/platform-model/",
      "status": "available"
    },
    {
      "id": "platform.users-and-roles",
      "title": "Users and roles",
      "summary": "Each Workspace has one owner. Administrators manage the Workspace, while developers can view product data and run scans without administrative access.",
      "path": "/overview/users-and-roles/",
      "status": "available"
    },
    {
      "id": "platform.workspace-access",
      "title": "Workspace access",
      "summary": "Membership is granted independently for each Workspace. A user may own, administer, or develop in more than one Workspace.",
      "path": "/overview/users-and-roles/#developer",
      "status": "available"
    },
    {
      "id": "platform.activity-usage",
      "title": "Activity and API usage",
      "summary": "Workspace owners and administrators can review bounded administration events and 30-day per-user API request and hosted-scan counters.",
      "path": "/overview/activity-and-api-usage/",
      "status": "available"
    },
    {
      "id": "platform.connections-repositories",
      "title": "Connections and repositories",
      "summary": "Connecting GitHub makes repositories accessible to a Workspace. Selection, plan capacity, and policy determine whether Supply Chain continuously monitors each repository.",
      "path": "/overview/connections-and-repositories/",
      "status": "available"
    },
    {
      "id": "platform.api-access",
      "title": "API access",
      "summary": "Personal API Tokens are user-owned, Workspace-scoped, expiring, revocable, and limited to explicit read or hosted-scan scopes.",
      "path": "/overview/api-access/",
      "status": "available"
    },
    {
      "id": "platform.mcp-setup",
      "title": "MCP setup",
      "summary": "Connect an MCP-compatible AI tool with browser OAuth. Signals Corps enforces the signed-in user's current Workspace membership and role on every request.",
      "path": "/overview/mcp/",
      "status": "available"
    },
    {
      "id": "supply-chain.scan-lifecycle",
      "title": "How scanning works",
      "summary": "Supply Chain validates bounded untrusted input, scans it with pinned rules under trusted policy, records the result, and deletes extracted source without running repository code.",
      "path": "/supply-chain/scanning/#scan-lifecycle",
      "status": "available"
    },
    {
      "id": "supply-chain.github-required-checks",
      "title": "Protect pull requests with GitHub checks",
      "summary": "Require the Signals Corps Supply Chain check in a GitHub ruleset so stable, high-confidence High and Critical findings can block under the Recommended policy.",
      "path": "/supply-chain/github-merge-protection/",
      "status": "available"
    },
    {
      "id": "supply-chain.scan-result",
      "title": "Scan result",
      "summary": "A result records immutable source identity, policy and ruleset provenance, coverage, completeness, duration, conclusion, and bounded findings. Scanner errors are failures.",
      "path": "/supply-chain/scans-and-results/",
      "status": "available"
    },
    {
      "id": "supply-chain.scan-status-conclusion",
      "title": "Scan status and conclusion",
      "summary": "Status describes whether work is queued, running, completed, or failed. Conclusion describes the policy outcome only after the scan produces an authoritative result.",
      "path": "/supply-chain/scans-and-results/#scan-states",
      "status": "available"
    },
    {
      "id": "supply-chain.coverage-completeness",
      "title": "Coverage and completeness",
      "summary": "Coverage records discovered, scanned, and skipped files. Completeness says whether every required target was inspected; an incomplete scan cannot produce a clean enforcement result.",
      "path": "/supply-chain/scans-and-results/#coverage-and-completeness",
      "status": "available"
    },
    {
      "id": "supply-chain.findings-evidence",
      "title": "Findings and evidence",
      "summary": "A finding identifies a managed rule match. Evidence is bounded and redacted, with an exact line range or file precision where available, and never includes complete private files.",
      "path": "/supply-chain/findings-and-evidence/",
      "status": "available"
    },
    {
      "id": "supply-chain.rules",
      "title": "Managed rules",
      "summary": "Managed rules have stable IDs, severity, lifecycle status, customer-safe descriptions, and optional knowledge-base mappings. Workspace occurrence counts remain isolated.",
      "path": "/supply-chain/rules-and-policy/#managed-rules",
      "status": "available"
    },
    {
      "id": "supply-chain.policy",
      "title": "Policy profiles",
      "summary": "Policy is stored outside inspected source. The Workspace's plan selects available rule coverage and whether matches only alert or can create an automated blocking outcome.",
      "path": "/supply-chain/rules-and-policy/#policy-profiles",
      "status": "available"
    },
    {
      "id": "supply-chain.on-demand",
      "title": "On-demand scanning",
      "summary": "Authorized users can submit bounded text, ZIP, public repository, and CLI inputs. Signals Corps treats every input as untrusted and never runs repository code.",
      "path": "/supply-chain/on-demand-scanning/",
      "status": "available"
    },
    {
      "id": "supply-chain.plans-capacity",
      "title": "Plans and capacity",
      "summary": "Each Workspace has separate repository-monitoring capacity and hosted-scan allowance. Limits block new work instead of creating automatic overage charges.",
      "path": "/supply-chain/plans-and-capacity/",
      "status": "available"
    },
    {
      "id": "assistant.sources",
      "title": "The Captain's sources",
      "summary": "The Captain uses public Signals Corps docs for product concepts and typed authorized tools for authorized live data. It has no browser, general web search, shell, or arbitrary HTTP access.",
      "path": "/assistant/#sources",
      "status": "available"
    },
    {
      "id": "assistant.confirmation-retention",
      "title": "Captain confirmation and retention",
      "summary": "Writes require a durable preview and explicit confirmation. Conversations are retained for 14 days; separate audit records do not contain message text.",
      "path": "/assistant/#actions-and-confirmation",
      "status": "available"
    }
  ]
}