UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

AI Memory

next-recursive-prompt.uai

Carries the compact next-loop resume prompt for code-bearing agents without replacing authoritative .uai records or current human instruction. next-recursive-prompt.uai is required for agents that deal with code, automation, executable workflows, or code-like artifacts. It is not required for agents that don't deal with any coding..

  • Record UAIX-MEMR-3090
  • Path /es-us/ai-memory/uai-files/next-recursive-prompt-uai/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-MEMR-3090
Surface
AI Memory
Access
Public and linkable

How to use this page

Use this file detail page to confirm the exact required scope, review requirement, no-op trigger, and related .uai records before relying on the file in a package.

Package memory path

AI Memory Package WizardProject HandoffAgent File HandoffAGENTS.md Specification

Required File Sets

Every .uai file belongs to a declared package scope

Use this guide to keep package files in one of the closed UAIX states: universal required, profile-required, content-triggered required, configuration-specific required, or out of scope.

Universal

Five launch-baseline anchors travel first

identity.uai, world-context.uai, totem.uai, taboo.uai, and short-term-memory.uai are required for every launch-baseline UAIX memory or handoff package.

Profile

Declared package type controls the rest

Project Handoff, Agent File Handoff, Long-Term Memory, LLM Wiki, and release-bound packages each carry their own required file set.

No-code assistants

Coding standards stay out of scope until code-like work exists

.uai/coding-standards.uai and .uai/next-recursive-prompt.uai are required for project/developer and code-bearing packages; both are out of scope for no-code assistant packages until code, automation, executable workflow, or code-like artifacts are declared or detected. next-recursive-prompt.uai is not required for agents that don't deal with any coding. In code-bearing packages, its stored plan is used for continuation, resume, keep-going, do-the-next-thing, or directly related requests.

Package memory path

AI Memory Package WizardGenerate supported file sets from the canonical source rules.Project HandoffProject-startup package profile and read order.Agent File HandoffLocal file intake, disposition, archive, and proof-of-use path.AGENTS.md SpecificationFront-door project guidance and local memory discovery.
Core ruleClosed file states
universal required | profile-required | content-triggered required | configuration-specific required | out of scope

Validators and agents should rely only on files required for the declared package scope and ignore out-of-scope files as absent.

Carries the compact next-loop resume prompt for code-bearing agents without replacing authoritative .uai records or current human instruction.

File .uai/next-recursive-prompt.uai
Category Developer and release evidence files
Required status next-recursive-prompt.uai is required for agents that deal with code, automation, executable workflows, or code-like artifacts. It is not required for agents that don't deal with any coding.
Main reader Developer agent, automation agent, workflow agent, and reviewer
Update frequency After meaningful work, test results, blockers, deployment, handoff, intake processing, or context compaction.
Human review requirement Required when the next-loop prompt changes release scope, authority, public claims, or deployment actions.
No-op trigger type Missing, stale, invalid, contradictory, or evidence-broken next-recursive prompt in a required code-bearing scope.

next-recursive-prompt.uai is not required for agents that don't deal with any coding.

What this file is

A derived hot-memory resume artifact using canonical JSON profile uaix.next-recursive-prompt.v1. It is not a second source of truth.

Why necessary

Recursive coding sessions often lose the exact next work chunk after compaction or handoff. This file keeps the next loop executable while forcing authoritative records to win on conflict.

When required

next-recursive-prompt.uai is required for agents that deal with code, automation, executable workflows, or code-like artifacts. It is not required for agents that don't deal with any coding..

What belongs

  • The next safe work chunk and acceptance evidence.
  • Authoritative source references to read before acting.
  • Checks to run and blocked-recovery behavior.
  • Refresh triggers and writeback targets for the next loop.

What does not belong

  • Secrets, credentials, access tokens, private keys, or private incident details.
  • Durable project truth that belongs in short-term memory, progress, decisions, constraints, test-plan, stack, or architecture records.
  • Raw chat logs, broad speculation, or stale history that belongs in archives.
  • A YAML mirror or alternate source of truth.

How receiving AI should use it

  • Read authoritative_refs before using the prompt.
  • Use the stored plan when the user asks to continue, keep going, do the next thing, resume, proceed, or otherwise continues the recorded next loop.
  • When the current request directly relates to the stored next loop, review this file for useful plan ideas before discarding or superseding it.
  • When the user gives a specific unrelated instruction, current user instruction governs the turn and this file is regenerated after accepted work.
  • Treat the file as derived hot-memory only.
  • If it conflicts with authoritative .uai records, stop and regenerate it from those records.
  • Fail closed or enter blocked recovery when the file is stale, invalid, contradictory, or points to missing evidence in a required code-bearing scope.

How human reviewer should use it

  • Confirm the file is JSON with profile uaix.next-recursive-prompt.v1.
  • Confirm it names the exact next work chunk, checks, blockers, and update targets.
  • Confirm no secret or private credential is present.
  • Confirm it does not override authoritative .uai records.

Scenario examples

  • After a long coding pass, regenerate the file so the next agent can continue without replaying the full transcript.
  • When a human says keep going, use it to recover the next work chunk after reviewing authoritative memory.
  • When a human asks for an unrelated task, review it only for relevant context, then follow the current request and regenerate afterward.
  • After a failed test run, record the blocker and the next recovery step.
  • After processing active intake, point the next loop at the updated ledger and remaining work.

No-op and human-review triggers

  • The file is required but absent from a code-bearing package.
  • The file is not valid JSON or does not use profile uaix.next-recursive-prompt.v1.
  • The next-loop prompt contradicts short-term memory, progress, constraints, coding standards, stack, architecture, or test-plan.
  • The file contains secrets or unsupported public claims.

Update and maintenance rules

  • Regenerate after meaningful work, test results, blockers, deployment, handoff, intake processing, and context compaction.
  • Keep bulky history in archives and preserve only the current next-loop slice here.
  • Write accepted current truth into authoritative .uai records first, then regenerate this file from those records.

Relationship to other .uai files

  • Derived from AGENTS.md, identity, world-context, Totem, Taboo, short-term memory, startup packet, system profile, receiver brief, coding standards, stack, architecture, context, constraints, progress, current state, next actions, test plan, and manifest.
  • Short-term memory keeps current truth; this file keeps the next recursive prompt.
  • Progress and test-plan carry evidence; this file points to the next action and checks.

Minimal example

Code example
# next-recursive-prompt.uai
file: .uai/next-recursive-prompt.uai
required_status: next-recursive-prompt.uai is required for agents that deal with code, automation, executable workflows, or code-like artifacts. It is not required for agents that don't deal with any coding.
owner: human-reviewed owner or steward
current_state: accepted current record for this package scope
no_op_trigger: Missing, stale, invalid, contradictory, or evidence-broken next-recursive prompt in a required code-bearing scope.
evidence: link or local pointer to reviewed source
last_reviewed: YYYY-MM-DD

Completeness checklist

  • Top-level fields match uaix.next-recursive-prompt.v1.
  • Authoritative refs are present and current.
  • Next loop names a concrete work chunk, checks, blockers, and writeback policy.
  • No secrets, private credentials, unsupported claims, or stale instructions are present.

Common mistakes

  • Using it as a second source of truth.
  • Letting it override a newer unrelated human instruction.
  • Discarding a related stored plan without reviewing it for useful work ideas.
  • Letting it survive after authoritative records changed.
  • Storing a full chat transcript instead of a compact next-loop prompt.
  • Adding it to no-code assistant packages before code, automation, executable workflow, or code-like artifacts are declared or detected.

Machine-readable digest

Agents should treat this digest as page-orientation evidence, not runtime authority.