Skip to content
View ndrorchestration's full-sized avatar
🤸‍♂️
"Choreographing" your Orchestration
🤸‍♂️
"Choreographing" your Orchestration

Block or report ndrorchestration

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ndrorchestration/README.md

Andrew “Ndr / Ender” Hensel

AI Systems Designer · AI Orchestration Engineer · Evaluation · Governance

I design and evaluate AI systems with a focus on multi-agent orchestration, prompt systems, evaluation methodology, provenance, governance, reproducible experimentation, and trustworthy deployment controls.

My primary body of work is DGAF (Dynamic Governance Agentic Formation), an evolving research and implementation framework for governed agentic systems. The associated PDMAL (Phi-Driven Multi-Agent Lattice) track investigates multi-agent topology and control experimentally.


Current Focus

DGAF — Dynamic Governance Agentic Formation

DGAF combines agent orchestration, governance gates, evidence handling, provenance, semantic controls, evaluation, and deployment safeguards into a governed control-plane architecture.

Recent engineering work includes a governed recursive control-plane with bounded recursion, immutable governance envelopes, exact state identity and cycle detection, append-oriented provenance, explicit proposal/authorization/commit barriers, capability-boundary tests, hardened lifecycle semantics, audit sealing, exact-head CI checks, source-SHA attestation, and candidate-bound evidence reconciliation.

The current engineering cycle is extending that foundation into a fail-closed confidential-execution path for blinded experimental work. This work covers authenticated attestation verification, explicit pre-execution authorization consumption, in-process key generation, blinded output/manifest binding, post-execution attestation, crash/retry controls, and end-to-end lineage verification. These controls are being developed and tested before any empirical experiment is authorized.

PDMAL — Phi-Driven Multi-Agent Lattice

PDMAL is the associated experimental research track. It is designed around deterministic execution, topology generation, blinded comparisons, artifact schemas, provenance, reproducibility, and pre-specified statistical analysis.

Current experimental state: Epoch 001 is retained historical blinded collection evidence (50 paired seed units / 2,250 observations) whose protected mapping is cryptographically unrecoverable; its primary analysis is therefore UNANALYZABLE / NOT RUN. The prospective successor Track A is PRE-FREEZE / FAIL-CLOSED / NOT AUTHORIZED / N=0. Canonical DGAF/PDMAL efficacy is NOT ESTABLISHED. Passing CI, synthetic/dry-run evidence, deployment readiness, or historical verification is not treated as experimental efficacy.


Areas of Work

  • AI orchestration and multi-agent systems
  • Prompt engineering and prompt evaluation
  • AI evaluation, QA, and benchmark methodology
  • Governance, provenance, and evidence architecture
  • Agent control-plane design
  • Runtime and deployment verification
  • Adversarial testing and failure-mode discovery
  • Reproducible experimental infrastructure
  • Semantic and ontological boundary governance
  • Spatial and acoustic intelligence research

Evidence Discipline

A central design principle of the work is to keep these states distinct:

defined → implemented → computed → verified → attested → historical → hypothesis → unsupported

A passing test, deployment, historical attestation, or repository claim is not automatically equivalent to independent verification or empirical efficacy. Exact candidate identity, execution context, run evidence, provenance, and scope matter.

The project deliberately records unresolved conditions rather than converting implementation maturity into success claims. Historical evidence is retained as provenance and is not silently transferred across candidate, deployment, run, or artifact boundaries.


Selected Projects

Project What it demonstrates Current evidence boundary
DGAF-Framework Governed multi-agent orchestration, provenance, evidence gates, confidential-execution research Epoch 001 retained but primary analysis unanalyzable; successor experiment remains PRE-FREEZE, NOT AUTHORIZED, N=0; efficacy not established
Orbit-Driftwatch Observable multi-agent workflow, provider boundaries, web retrieval, claim→source provenance, portable run artifacts Deterministic and contract tests pass; live hosted execution and public showcase deployment remain open gates
Driftwatch Drift instrumentation, failure-aware evaluation, reproducible synthetic benchmark apparatus Implementation and synthetic benchmark verified; real-world calibration/efficacy not established
Morse-Orchestration Phase-preserving orchestration research, seeded synthetic experiments, paired analysis Synthetic research apparatus verified; model/production efficacy not established
sentinel-governance Fail-closed repository repair governance and mutation validation Operator/validation checks pass; autonomous semantic correctness is not established
resumeapex-eval Executable evaluation harness, known-answer controls, deterministic reproduction Harness CI/reproducibility verified; not a model-performance certification
agent-control-plane Minimal control-plane kernel, capability dispatch, rejection provenance, portable manifests Local kernel behavior tested; distributed/production controls remain outside current scope
Meshsense Exact source→deployment→runtime provenance and observable runtime state Deployment identity verified; physical sensing efficacy remains separate/unverified
ai-prompt-systems-portfolio Prompt/evaluation specifications and recruiter-readable prompt engineering artifacts Specifications are not presented as an executable evaluator; executable evaluation lives in ResumeApex

Portfolio Architecture

NDR AI Systems
├── Orchestration
│   ├── DGAF / PDMAL
│   ├── Orbit-Driftwatch
│   ├── Morse-Orchestration
│   └── Agent Control Plane
│
├── Evaluation
│   ├── Driftwatch
│   ├── ResumeApex
│   └── Prompt-system evaluation specifications
│
├── Governance
│   ├── Sentinel Governance
│   ├── Evidence / provenance controls
│   ├── Semantic boundaries
│   └── Runtime / deployment verification
│
└── Spatial / Experimental Interfaces
    ├── ASIS / Acoustic-Mesh
    ├── MeshSense
    └── Phi-Calculus

Current Engineering Snapshot — 2026-09-06

The portfolio now contains several executable verification surfaces rather than architecture documents alone:

  • DGAF has a broad exact-head CI/governance surface. Epoch 001 is historical retained collection evidence whose primary analysis is unanalyzable; the successor track remains PRE-FREEZE / NOT AUTHORIZED / N=0 and efficacy is not established.
  • Orbit-Driftwatch has deterministic orchestration, a server-backed provider boundary, source-bound web retrieval, explicit unsupported/conflicting-claim handling, and portable run artifacts; live hosted execution and public deployment are still open.
  • Driftwatch has a hardened build/dependency lane plus a retained synthetic detector benchmark, without promoting that synthetic result to real-world efficacy.
  • Morse-Orchestration has a validated seeded synthetic harness and paired research methodology.
  • Sentinel Governance has a fail-closed repair-mutation boundary and current dependency/validation checks.
  • ResumeApex has an executable deterministic evaluation harness with known-answer controls and a green current-main verification workflow.

The highest-value remaining work is increasingly integration and external validation rather than basic implementation: public Orbit deployment, a real provenance-retained hosted Orbit run, DGAF candidate/freeze/authorization progression, representative real-world Driftwatch calibration data, and independently reviewed evidence at the gates that require it.


Public Project Principles

  • Build the apparatus before claiming the result.
  • Preserve exact source and evidence identity.
  • Fail closed when required evidence is absent.
  • Treat adversarial findings as development signals, not embarrassments to hide.
  • Keep internal/private working records separate from public claims.
  • Distinguish governance-framework resemblance from legal or regulatory compliance.
  • Keep commercial, certification, and endorsement claims scoped to explicit evidence.

Contact / Professional Direction

My current professional focus is AI systems design, AI orchestration, evaluation, prompt engineering, governance, and trustworthy AI infrastructure, with particular interest in roles involving AI evaluation, model quality, prompt systems, agentic workflows, QA, reproducible experimentation, and governance-aware AI engineering.

I am especially interested in work where careful evaluation, evidence quality, provenance, and system-level reasoning matter as much as producing a working prototype.


Public profile last reconciled: 2026-09-09. Project status is maintained in each repository's authoritative evidence and governance records; this profile is a public representation, not an experimental source of truth.

Pinned Loading

  1. DGAF-Framework DGAF-Framework Public

    Dynamic Governance Agentic Formation Framework — NDR pattern registry, AXIS constraints, multi-agent governance protocols, and SWEEP_LOG. Spine of the ndrorchestration AI governance ecosystem.

    Python 4

  2. Driftwatch Driftwatch Public

    Phi-driven multi-agent synthesis simulation with real-time drift detection, truth scoring, and harmonic state monitoring

    TypeScript 1

  3. agent-control-plane agent-control-plane Public

    Python

  4. Morse-Orchestration Morse-Orchestration Public

    Project: MORSE — Multi-Orbital Resonance Scheduling ExperimentArchitecture under test: MOLI — Multi-Orbital Loop Interchange

    Python

  5. Orbit-Driftwatch Orbit-Driftwatch Public

    Observable Multi-Agent Reasoning

    JavaScript