iiRecord
Agentic AI Atlas · Reusable Atlas Views
page:viewsa5c.ai
II.
Page JSON

page:views

Structured · live

Reusable Atlas Views json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · wiki/views/README.mdCluster · wiki
Record JSON
{
  "id": "page:views",
  "_kind": "Page",
  "_file": "wiki/views/README.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Reusable Atlas Views",
    "displayName": "Reusable Atlas Views",
    "slug": "views",
    "articlePath": "wiki/views/README.md",
    "article": "# Reusable Atlas Views\n\nReusable views are wiki-backed projections that render graph records with a named UI template instead of plain markdown alone.\n\nThe first supported template is the `service-tower` view learned from the a5c Service Tower static page. It keeps the original idea of a stacked isometric building, but makes the floors, rooms, service lines, and record links configurable from wiki frontmatter.\n\n## Available examples\n\n| Page | Projection |\n|---|---|\n| [`service-tower.md`](./service-tower.md) | A broad Atlas catalog tower across schema, stack, and operations records. |\n| [`agent-stack-tower.md`](./agent-stack-tower.md) | A tower focused on the universal agentic stack and runtime implementations. |\n| [`quality-tower.md`](./quality-tower.md) | A tower focused on claims, evidence, CI surfaces, workflows, and quality records. |\n| [`library-tower.md`](./library-tower.md) | A tower focused on generated process-library assets. |\n\n## Template contract\n\nAdd this frontmatter to a wiki page:\n\n```yaml\nreusableView:\n  type: service-tower\n  options:\n    title: \"My Tower\"\n    subtitle: \"What this projection explains\"\n    floors:\n      - id: \"floor-id\"\n        label: \"FLOOR LABEL\"\n        subtitle: \"What the floor groups\"\n        rooms:\n          - id: \"room-id\"\n            label: \"Room label\"\n            color: \"#D4A84B\"\n            query:\n              kind: \"Workflow\"\n              cluster: \"workflows\"\n              limit: 8\n```\n\nRooms can query by `kind`, `cluster`, free-text `search`, or explicit `ids`. Each room becomes a graph-backed catalog chamber with record links and service-line summaries.\n",
    "documents": [
      "page:views-service-tower",
      "page:views-agent-stack-tower",
      "page:views-quality-tower",
      "page:views-library-tower"
    ]
  },
  "outgoingEdges": [
    {
      "from": "page:views",
      "to": "page:views-service-tower",
      "kind": "documents"
    },
    {
      "from": "page:views",
      "to": "page:views-agent-stack-tower",
      "kind": "documents"
    },
    {
      "from": "page:views",
      "to": "page:views-quality-tower",
      "kind": "documents"
    },
    {
      "from": "page:views",
      "to": "page:views-library-tower",
      "kind": "documents"
    },
    {
      "from": "page:views",
      "to": "page:views-agent-stack-tower",
      "kind": "contains_page"
    },
    {
      "from": "page:views",
      "to": "page:views-library-tower",
      "kind": "contains_page"
    },
    {
      "from": "page:views",
      "to": "page:views-quality-tower",
      "kind": "contains_page"
    },
    {
      "from": "page:views",
      "to": "page:views-service-tower",
      "kind": "contains_page"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:index",
      "to": "page:views",
      "kind": "contains_page"
    }
  ]
}