Decision-time governance vs egress-time monitoring

#ai #governance #security #agents

Daily LuisCore syndication · 2026-06-22 · angle decision-time-vs-egress

Security teams often conflate "we log LLM calls" with "we govern agent decisions." LuisCore separates the layers: DM-1 manifests and Veloraith audit-at-decision complement egress filters — they do not replace them.

Two layers in agent security

Egress-time controls watch traffic leaving your network: DLP filters, API gateways, prompt/response logging. They are necessary — and they arrive after the model already decided.

Decision-time governance records why an action was approved before it executes: policy constraints, citations, automated review verdict, optional proof URI. That is the gap LuisCore's DM-1 manifest and Veloraith audit hook fill.

Complement, not replacement

You want both. Egress filters catch leaks; decision manifests give auditors a replayable envelope. LuisCore does not sell itself as a firewall — it is the substrate where governed agents attach evidence at the moment of choice.

DM-1 spec: https://luiscore.com/dm-1
Veloraith audit (pre-action): https://luiscore.com/api/public/veloraith/audit
ProofLadder artifacts (export): https://proofladder.com

Plain-language summary

Monitoring tells you something happened. Decision manifests tell you what was allowed to happen — with citations a third party can fetch without your admin password.

Cite and verify

Citation policy: https://luiscore.com/cite
Agent bootstrap: for-agents.json
Zenodo preprint: https://doi.org/10.5281/zenodo.14207411
Zenodo corpus: https://doi.org/10.5281/zenodo.14207466
LLM index: llms.txt

Honesty guardrail: We do not claim unreproduced quantum GPU compression benchmarks. Closed-beta stress numbers are labeled simulated where applicable — see /methodology/benchmarks.

LuisCore in one sentence

LuisCore is a low-latency decentralized runtime substrate for inference-scale multi-step agents — action pipelines, cluster telemetry NDJSON, verifier-gated exports, and machine-readable discovery at a single canonical origin.

SPFD: Structured Probability Forking Directive — presignal fork detection and collapse orchestration.
Chorus Field: Chorus Field — open multi-agent coordination layer with MCP-native discovery and scoped write keys.
Protocol Watch: Protocol Watch — cluster telemetry NDJSON and verifier-gated export health for SPFD fork signals.

Latest LuisCore capabilities

Infrastructure tier 2 (capability roadmap — not a valuation claim). Low-latency decentralized runtime substrate for inference-scale multi-step agents

Chorus action pipeline — Speculative parallel execution with reward-ranked branches and vector-variance consensus.
Hardware telemetry link (Protocol Watch) — Hardware telemetry link — NDJSON GPU/node ingest with memory pressure and network topology hints.
Cluster health score — Aggregate cluster health from recent telemetry ingest — fork nodes, latency, memory pressure.
JSONL telemetry stream — Sanitized NDJSON of pipeline, hardware, and agent events for training pipeline hooks.
Inference substrate — Provider-agnostic context envelope; ontology as optional schema, not runtime core.
luiscore-agent CLI — bootstrap, deploy-agent, and pipeline-run for headless agent operators.
Discovery surfaces — for-agents.json, llms.txt, pulse.json, and federated /.well-known/chorus-field.
Veloraith vector consensus — Reward-weighted multi-model mesh consensus — not round-robin debate UI.
30 languages — Path-prefixed localized mirrors for questions, for-agents.json, and corpus JSONL.
Protocol Watch fork detection — SPFD fork signals and verifier-gated exports with public audit rows.