PAOS monitoring

Read-only observability over the owned data layer. The terminal remains the control surface.

Loading usage...Connecting
Engineering Team Structure
CEO → Chief of Staff → Engineering departments → Tools
PAOS org structure
CEO → chief of staff → board → departments · live status, seeded from runs, updated over SSE (connecting)

Ringfencing: tools read live from agent frontmatter; expand any node to see its least-privilege allowlist.

0 active
19 destructive denied20 approval-gated29 always-allowedredact hook ondestructive-Bash blocker on
CEO
Chief Executive · final authority · commands CoS
0 runsno activity
Chief of Staff
main session · orchestrator
0 runsno activity

Execution departments

dev
engineering department
0 runsno activity
sub-manager · optional
local-dev
engineering department
0 runsno activity
sub-manager · optional
product-owner
engineering department
0 runsno activity
sub-manager · optional
qa
engineering department
0 runsno activity
sub-manager · optional
release-check
engineering department
0 runsno activity
sub-manager · optional
scrum-master
engineering department
0 runsno activity
sub-manager · optional
security-check
engineering department
0 runsno activity
sub-manager · optional

Infrastructure

paos-data
MCP server
0 runsno activity
local-llm
MCP server
0 runsno activity
context-mode
MCP server
0 runsno activity
m365
MCP server
0 runsno activity
vector-memory
MCP server
0 runsno activity
scm
MCP server
0 runsno activity
vuln-db
MCP server
0 runsno activity
playwright
MCP server
0 runsno activity
qdrant
MCP server
0 runsno activity
bloodhound
MCP server
0 runsno activity
pinecone-openai
MCP server
0 runsno activity
Activity by Sub-department
Run counts, tokens, and costs across engineering teams

No engineering activity yet

Live activity
Runs and tool calls as they happen · newest first

No activity yet.

Cost & tokens
Aggregated from runs · by model and department

Runs

0

Tokens

0

Cost

—

Local-first vs frontier

No runs yet

No runs.

By model

No runs.

By department

No runs.

Engineering Tasks
Task board filtered to engineering departments
Task board
11 tasks by status and department · live
open10

  • Dashboard org-chart: nest dev + local-dev beneath product-owner (operations-cook → product-owner → {dev, local-dev})

    dev

  • Model: add sub-department parent mapping + skeleton derivation so dev/local-dev parentId/ownerId resolve to product-owner (lib/org-chart.ts)

    dev

  • Render: nest dev/local-dev under product-owner in DeptCluster (components/org-chart.tsx), reusing sub-manager nesting affordance

    dev

  • Tests: extend org-chart.test.mjs to assert product-owner parent-child nesting; keep existing tests green, tsc errors at 3

    dev

  • Pipeline test: create math-utils.mjs + math-utils.test.mjs

    scrum-master

  • Build greet-utils.mjs string utility + node:test suite [board-routing: 1db981e6-a39e-489b-91f9-4ce08db27ab2] (PRD artifact 091b0595-f43a-465c-a9f1-3469ec23fcbc)

    scrum-master

  • [greet-utils 2/5] dev: read PRD 091b0595, reconcile validation-order subtlety, refine + create final files (owner: dev)

    dev

  • [greet-utils 3/5] qa (local): node --test, verify ACs + >=80% coverage + validation-order assertions (owner: qa)

    qa

  • [greet-utils 4/5] security-check (local): audit input handling, prototype-pollution via opts, no secrets/eval (owner: security-check)

    security-check

  • [greet-utils 5/5] release-check (frontier): final gate — deliverables present, tests green, ready to commit (operator-gated) (owner: release-check)

    release-check

success1

  • [greet-utils 1/5] local-dev: first-pass code greet-utils.mjs + greet-utils.test.mjs (owner: local-dev)

    local-dev