PHP graphs of _AugmentedIntelligence

What graphs can be built in PHP, what is implemented now, data sources, and how to extend.

Related: ProgramStatePortal.md · IisPhpIntegration.md · MinecraftWebDashboard.md · BrainstormIntegrations.md · PhpPluginPanelsBrainstorm.md (plugin panels, more graphs, local/remote control)

Plugin panels brainstorm (summary)

See PhpPluginPanelsBrainstorm.md for a full catalog of:

• PHP plugin panel host (registry, lazy load, packs)
• Graph panels (gov pipeline, market, DQN, MathNN access, ethics, weather, …)
• Local / remote control panels (same command strings, dry-run, tokens, multi-host)

Design principle

PHP is a read-only visualization layer. The C++ host exports JSON; PHP serves and charts it (Chart.js, canvas, optional vis-network later).

_AugmentedIntelligence
  portal export / graphs export / minecraft state.json
        │
        ▼
  program_web_portal/api.php  (or minecraft_web_dashboard/api.php)
        │
        ▼
  Browser charts (Chart.js)

Implemented now

Export (C++)

graphs architecture    # node–edge architecture DAG JSON
graphs discovery       # categories, posted/pending, entries
graphs rl              # portal RL/overview slice + cutlass status
graphs all             # combined payload
graphs export          # write files to portal dir + php site data/
integrate all          # includes graphs export path

Files written by graphs export

Default portal dir is typically C:/_AugmentedIntelligence/web_portal (see portal settings).

PHP API

GET api.php?q=graphs
GET api.php?q=graphs&which=all
GET api.php?q=graphs&which=architecture
GET api.php?q=graphs&which=discovery
GET api.php?q=graphs&which=rl

Searches portal graphs/ next to state.json, then program_web_portal/data/.

PHP UI (program_web_portal)

Graphs nav section:

Minecraft dashboard (separate)

Already charts:

• Players / avg health / avg food
• Hostiles / world time
• Bridge connected

See MinecraftWebDashboard.md.

Architecture graph schema

{
  "type": "architecture",
  "nodes": [
    { "id": "camera", "label": "Camera", "category": "sensor", "status": "live" }
  ],
  "edges": [
    { "from": "camera", "to": "vision", "label": "frames" }
  ]
}

Categories used: sensor, perception, memory, model, action, ui, control, extensibility.

Nodes include camera, audio, commands, vision, memory, llm, cutlass, discovery, wordpress, portal, iis, web, plugins, etc.

Discovery graph schema

{
  "type": "discovery",
  "auto_post": false,
  "dry_run": true,
  "total": 24,
  "pending": 20,
  "posted": 4,
  "by_category": { "perception": 3, "cognitive": 2 },
  "entries": [
    {
      "id": "disc-1-…",
      "title": "…",
      "category": "session",
      "posted": false,
      "created_utc": "…",
      "epistemic": "method"
    }
  ]
}

Full catalog of graphs you can build in PHP

Already easy with current exports

Ready with small JSON additions

Chart types that fit PHP front ends

Libraries: Chart.js (in use), ApexCharts, ECharts, Plotly.js, vis-network, Leaflet, Mermaid.

How to run the Graphs UI

# In the app
portal enable
portal export
graphs export
# or: integrate all

# Terminal
cd program_web_portal
# edit config.php: $state_file path if needed
php -S 0.0.0.0:8090

Open http://localhost:8090/ → Graphs.

Lua

print(graphs_architecture())
print(graphs_discovery())
print(graphs_export())

Security

• Graphs and portal are read-only.
• Do not put MySQL passwords in public repos; use env / config.php locally.
• Bind PHP server to trusted LAN when exporting operational state.

Files

• BrainstormIntegrations.cpp — graph builders + export
• program_web_portal/api.php — q=graphs
• program_web_portal/index.php — Graphs section
• ProgramStatePortal — state.json / history for RL trends