A front door for BlackNode. Agentic orchestration behind a conversational pane of glass. The live engine runs at Core — this page is the map, not the machine.
Core is built to take architectural intent and run a closed loop — not a one-shot snippet. Scan context, generate typed code, audit for secrets, and hand back a complete, executable file. That cycle lives in Core, not on this page.
STANDARD AI // LEGACY_MODE
ISOLATED SNIPPETS
A text prompt in, a partial function out, often with a TODO still sitting in the body. The cycle stops short of something you can run.
BLACKNODE CORE // TEXT_IN::V3.0
01 SCAN 02 TYPED 03 AUDIT
Multi-file context, type-safe generation, and a zero-secret audit. Status in Core reads CYCLE_COMPLETE // READY_DEPLOY when the loop finishes.
02 // ORCHESTRATION TOPOLOGY
The Four Agentic Pillars
Planning, Coding, Review, and Operations — the same cycle the Orchestrator drives in Core.
QUADRANT A // PLANNING
Architectural Orchestration
Break a goal into decoupled services, state schemas, and a dependency graph before any file is written.
QUADRANT B // CODING
Multi-File Implementation
Deep workspace scans, low-overhead execution, and patches in unified Git diff format.
QUADRANT C // REVIEW
Automated Governance
OWASP-style vulnerability checks and secret protection. Credentials are not stored in the page.
QUADRANT D // OPERATIONS
Autonomous Triage
Parse runtime logs, isolate the failing line, and deploy a diagnostic patch from inside Core.
03 // ORCHESTRATOR + VEHICLE
Orchestrator and the Godot Vehicle
The Orchestrator is the general brain above every vehicle: sessions, pipeline stages, brain tier, guardrails, and verification. Godot is the proof — a live viewport that runs what the agent compiles. Both live in Core.
04 // CORE ORCHESTRATOR
Sessions, stages, verification
A conversational console for the whole platform. Prompt dispatch, persisted threads, and an independent verifier after compile. This is the product surface.
04B // VEHICLE_PROOF
GODOT VIEWPORT — LIVE IN CORE
A mobile-first Godot sandbox used as the proof-of-concept vehicle. Natural language in, typed GDScript and a playable scene out, in the same engine as the console.
04 // STUDIO OS
Docs, Grid, Vault, AI
An offline studio fused into Core. Local-first, keyless, and stored per user on the device.
DOCS
Offline markdown
Source on one side, rendered reading view on the other. Autosaves locally.
GRID
Formula sheet
A real engine for refs, ranges, SUM, IF, and the usual sheet functions. Export to CSV.
VAULT
On-device, per user
Secrets stay on the device and are redacted in the audit log. Nothing is uploaded.
NODECORE AI
Same brain tier
Tools-first retrieval over docs and sheets, then synthesis. No raw keys in the client.
05 // GUARDRAILS
Allow, Ask, Deny
Sensitive actions are gated in Core. Approvals happen there — this page does not run the engine, and it cannot approve anything on your behalf.
POLICY
ALLOW // ASK // DENY
Each rule can be cycled in Core. Ask prompts a one-time or session approval; deny blocks the action.
AUDIT LOG
Hash-chained
Every event lands in a tamper-evident chain you can verify and export.
VERIFIER
Independent second judge
A compile can face a second pass with no prior context from the first brain.
SECRETS
Zero credentials stored
The page does not keep organisation fingerprints or keys in code.
06 // ECOSYSTEM
The Rest of the Stack
Live cards open a public URL. Everything else is still on the workbench — tagged, not linked.