Skip to content

v4.1.0-rc3 — Delegation Receipt Observability

Pre-release
Pre-release

Choose a tag to compare

View all tags
@SuperDaddyV SuperDaddyV released this 13 Aug 09:52
· 54 commits to master since this release
v4.1.0-rc3
7890f17

v4.1.0-rc3 — Delegation Receipt Observability

This release candidate adds a concise Delegation Receipt to the installer-managed Global AGENTS policy.

The goal is observability, not increased Luna usage.

A task may correctly remain with Sol when delegation would add more coordination cost than value. RC3 makes that decision visible without lowering the delegation threshold or forcing child-agent creation.

What changed

For non-trivial tasks, the final response may now include one concise Sol/Luna receipt.

Examples:

Sol/Luna: Sol-only · task too small
Sol/Luna: Sol-only · reasoning/architecture task
Sol/Luna: Sol-only · no independent bounded work
Sol/Luna: Sol-only · Luna unavailable

When native Luna workers are actually used:

Sol/Luna: delegated · luna_max ×1

For verified overlapping direct child execution:

Sol/Luna: delegated · luna_max ×3 · parallel

Important behavior

The Receipt is descriptive only.

It does not:

  • lower the delegation threshold
  • force Luna usage
  • trigger an extra selector call
  • trigger an extra tool call
  • create an extra child
  • write telemetry or state
  • expose hidden chain-of-thought or child scratchpads

The Receipt summarizes execution facts already available to the parent task.

Why this matters

0 Luna does not automatically mean the installation failed.

Normal states include:

Sol-only
→ the task is too small, reasoning-heavy, or not safely separable

Sol → Luna
→ one clear bounded execution task exists

Sol → Luna ×2/3
→ multiple independent bounded tasks are worth parallel execution

RC3 makes these states easier for users to distinguish.

Runtime validation

Real RC1 → RC3 Global upgrade

PASS.

Observed upgrade:

effective changes = 2

Only the following installer-owned runtime content changed:

  • Global AGENTS managed block
  • install manifest metadata / owned hash

The following remained byte-unchanged:

  • Daily Selector
  • five Luna agent definitions
  • global config
  • Daily Profile
  • LKG

A second installer apply returned:

IDEMPOTENT_PASS

The transaction backup was retained and verified for rollback readiness.

Sol-only Receipt smoke

PASS.

Observed:

actual child count = 0

Sol/Luna: Sol-only · reasoning/architecture task

No extra selector, tool, child, repository write, or Global-state write was performed to produce the Receipt.

Delegated Receipt smoke

PASS.

Observed:

selected role = luna_max
direct children = 3
model = gpt-5.6-luna ×3
effort = max ×3
parallel = verified
grandchildren = 0

Final Receipt:

Sol/Luna: delegated · luna_max ×3 · parallel

Receipt role, child count, and parallel status matched parent-visible runtime evidence.

Sol independently verified the delegated results and retained final acceptance authority.

Delegation architecture remains unchanged

GPT-5.6 Sol
      ↓
Global / Project AGENTS policy
      ↓
Daily Selector
      ↓
Native Luna / selected daily effort
      ↓
Native leaf execution
      ↓
Sol Acceptance

The following remain unchanged:

  • Sol is the sole planner, orchestrator, ambiguity resolver, and final acceptance owner.
  • Luna is a bounded execution worker.
  • Five Luna roles remain: low, medium, high, xhigh, and max.
  • ultra remains excluded.
  • Maximum direct Luna concurrency remains 3.
  • Luna remains a native leaf.
  • Task Contract and Context Firewall remain unchanged.
  • Delegation threshold remains unchanged.
  • No Hook Router or custom orchestration engine is introduced.

Selector behavior remains unchanged

Valid same-day Daily Profile
        ↓
ModelDial Official API v1
        ↓ invalid / unavailable
Official Full Snapshot JSON
        ↓ invalid / unavailable
Valid LKG
        ↓
NO_LUNA_PROFILE_AVAILABLE

RC3 does not modify:

  • ModelDial API acquisition
  • snapshot fallback
  • LKG behavior
  • Beijing-day locking
  • same-day reuse
  • selection scoring
  • capability degradation
  • state schema

Installation

New users should use the immutable RC3 setup contract referenced by the repository README.

Existing RC1 users who want the Delegation Receipt should apply the RC3 installer upgrade through the documented setup contract.

The installer performs an existing-v4 transactional upgrade with ownership validation, backup, and rollback protection.

Validation

RC3 source validation:

Commit A:

fe9642f95fa7b66daa210217c1e66e4b43bd88bb

  • Windows CI: PASS
  • Ubuntu CI: PASS
  • macOS CI: PASS

Final documentation commit:

7890f17fbadfab96e16e07a640d561338c24c6c5

  • Windows CI: PASS
  • Ubuntu CI: PASS
  • macOS CI: PASS

Full repository suite:

109/109 PASS

Real runtime:

  • RC1 → RC3 upgrade: PASS
  • idempotency: PASS
  • rollback readiness: PASS
  • Sol-only Receipt: PASS
  • delegated Receipt: PASS
  • native leaf: PASS
  • Sol Acceptance: PASS

Documentation UX

The README now includes:

  • how to distinguish normal Sol-only execution from delegation
  • a reminder that 0 Luna != installation failure
  • a basic delegation self-test
  • an optional parallel delegation self-test

Release status

This is a prerelease.

v4.0.0 remains the current stable release.

Deferred hardening

Two selector hardening observations remain intentionally deferred:

  • stronger same-day profile validation
  • broader normalization of selected fetch/write exceptions

They are not part of RC3 and do not affect the Delegation Receipt feature validated here.

Attribution

ModelDial-derived test data remains attributed under CC BY 4.0 as documented in fixtures/modeldial/README.md.

Community project

This is an independent community project and is not affiliated with, sponsored by, or endorsed by OpenAI or ModelDial.

Assets 2
Loading