UAI project memory

Explains the local .uai memory package carried in the theme source for bounded cross-session handoff, not runtime execution or automatic synchronization.

Research
Last verified
Not verified
Updated
Reading time
1 minutes

Explains the local .uai memory package carried in the theme source for bounded cross-session handoff, not runtime execution or automatic synchronization.

Local handoff role

The theme source includes a .uai directory with typed current context, constraints, architecture, tests, versions, next actions, and release evidence. It is intended for humans and AI agents working on the source package.

Non-goals

The files do not execute code, modify WordPress, synchronize to an external service, certify the project, or replace owner review.

Scope

This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.

Engineering considerations

  • Identify the source, version, target environment, and owner.
  • Separate observed values from estimates and externally reported values.
  • Record trade-offs, unsupported cases, and fallback behavior.
  • Link performance statements to a compatible benchmark methodology.

Verification questions

  • What exact artifact, revision, backend, and environment were reviewed?
  • Which assumptions could change the result?
  • Which data should be retained so another engineer can reproduce the conclusion?