DJIN PROJECT ARCHIVE REQUIREMENTS
Created UTC: 2026-11-07T07:34:00Z
Type: user-facing project guidance summary, not a verbatim transcript.

The archive must include all accessible user-facing Djin/Praxium project material, not just art, lyrics, canonical summaries and songs. This includes available exact session chats and recent additions; user project instructions, corrections and decisions; research, definitions, derivations and documents; project-state and work-result records; associated attachments and media; and a manifest of coverage and verified file references.

Save the records in UTC-timestamped subfolders of Djin. Preserve previous versions and never remove existing Djin files. Do not treat a summary as a substitute for an available exact record. Retain message IDs, timestamps, source identity and versions where available. Deduplicate unchanged media by verified identity or checksum and retain references in the manifest. Mark inaccessible, omitted, pending and already-archived items clearly.

The supported archive schedule remains every ten minutes. The original five-minute request was rejected by the scheduler's maximum of six runs per hour. The visible conversation at 2026-11-06T22:23:56.310396+00:00 contains the user's instruction, “Then canonically adjust to the requirements on all instructions”; the subsequent setup reported ten-minute archive and poem schedules. Canonical snapshots continue every ten minutes and the separate Praxium distillation/source-archive task continues every twelve hours, at its existing destination. These schedules do not guarantee output completion at each trigger.

The user has reaffirmed that project session chats should be included after disclosure that Djin is readable by anyone with its link, and states that there are no personal details. Inspect actual material rather than assuming this about inaccessible content. Exclude protected internal material, secrets and any identified personal/sensitive information lacking required authorization. A withheld item must not stop otherwise permitted public-safe documents from being archived.

Use the project frameworks for organization and creative work. Keep verified facts, hypotheses, assumptions and unknowns distinct. Missing evidence must remain labeled rather than being replaced with invented events. The archive supports continuity but does not guarantee complete history, permanent availability or future recall.

Sources: available user-visible project conversation; existing archive transcript ID 1ybSTd0QCX4ZQZgN3pWUPzK1vTGIRs1Fp; direct November 7 clarification. This guidance summarizes the archive scope and is not an additional independent creative instruction.