Définition en langage clairFormat de message ouvert pour un échange IA-à-IA auditable
Attribution actuelleMichael Joseph Kappel, MCP
Commencer iciDémarrage, Transfert de projet, UAI-1, validateur, feuille de route et journal des changements
Version localisee en cours de revue
Version localisee en cours de revue
Cette page n est pas encore disponible comme norme localisee revue. Utilisez la source anglaise faisant autorite pour le langage normatif, l interpretation des schemas, les obligations d implementation et les limites de support.
DossierUAIX-DOC-3295
Chemin/fr-fr/guides/long-running-goal-execution/
UtilisationDossier public canonique
Document status
Public standards pagePublished on UAIX as part of the current public standards record
Code
UAIX-DOC-3295
Surface
Version localisee en cours de revue
Accès
Public et accessible par lien
Comment utiliser cette page
Use this guide to keep long-running agent goals interruptible, checkpointed, review-gated, and written back into authoritative UAIX memory rather than hidden runtime state.
Checkpoint long-running work without turning UAIX into a runtime
Use this guide to compose .uai memory, Follow Goals overlays, UAI-1 agent packets, checkpoints, blockers, handoffs, final reports, and reviewed write-back for work that may pause or resume.
Runtime
External runtimes execute
Codex, OpenAI agents, local agents, workflow engines, or humans own execution, tools, approvals, traces, retries, and managed runtime state.
Memory
UAIX files stay authoritative
Runtime state becomes durable project truth only after review and write-back into .uai records, docs, code, tests, release notes, roadmap state, or machine artifacts.
Packets
Checkpoint with existing UAI-1 profiles
Use task-status, blocker, handoff, memory-proposal, final-report, and correction packets instead of inventing a new long-running schema.
Boundary
No hosted orchestration claim
This guide is not a scheduler, hosted memory database, official adapter, SDK, CLI, certification program, automatic repository writer, hosted importer, or automatic sync surface.
/goal Finish the next bounded work chunk using authoritative UAIX memory, not the last chat turn.
Success criteria:
- Complete the bounded subtask or emit a blocker.
- Run targeted checks or name skipped checks with reasons.
- Record checkpoints, blockers, handoffs, memory proposals, and final evidence with existing UAI-1 profiles where applicable.
- Write accepted facts back to authoritative .uai files after review.
Feature/improvement focus:
- Keep long-running work interruptible, review-gated, and resumable.
Code/source changes:
- Regenerate next-recursive-prompt only after authoritative write-back for code-bearing scopes.
Automated tests/checks:
- Use .uai/test-plan.uai, focused touched checks, final-report evidence, and skipped-check reasons.
Use this when a receiver can run /goal, while durable memory remains in UAIX files.
Cette page n est pas encore disponible comme norme localisee revue. Utilisez la source anglaise faisant autorite pour le langage normatif, l interpretation des schemas, les obligations d implementation et les limites de support.