IDEAS, DOCUMENTED AS THEY EVOLVE
An evolving collection of creative systems, complex research, sound, imagery, observations, and the ideas connecting them. Every chapter is built from its original sources.
THE ARCHIVE / 001 — ∞
Individual Drive subfolders become complete editorial chapters: artwork first, followed by the original research, publications, session records, audio, and evolving context.
This entry brings together 1 source file across 1 editorial section, organized as one integrated record of PoeticAsymmetry UTC. Its source materials comprise documents & publications (1). The following overview draws directly from the …
This entry brings together 1 source file across 1 editorial section, organized as one integrated record of PoeticAsymmetry UTC. Its source materials comprise documents & publications (1). The following overview draws directly from the …
This entry brings together 1 source file across 1 editorial section, organized as one integrated record of PoeticAsymmetry UTC. Its source materials comprise documents & publications (1). The following overview draws directly from the …
↗This entry brings together 1 source file across 1 editorial section, organized as one integrated record of UTC art:regular:1794029906. Its source materials comprise artwork & visual studies (1). The following overview draws directly fr…
This entry brings together 1 source file across 1 editorial section, organized as one integrated record of PoeticAsymmetry UTC. Its source materials comprise documents & publications (1). The following overview draws directly from the …
↗This entry brings together 1 source file across 1 editorial section, organized as one integrated record of UTC art:regular:1794029306. Its source materials comprise artwork & visual studies (1). The following overview draws directly fr…
Djin.site approaches research, artistic practice, cybernetic design, and sound as connected records of an unfolding creative process. The archive is source-oriented: not a conventional blog with loosely attached files, but a library of entire contexts assembled into readable, playable, visual stories.
Each article preserves the evolution of the underlying work. New Drive folders become new articles; changes in existing source folders update the matching article.
Subscribe to the open RSS feed ↗A living, multidisciplinary document composed from 1 connected original sources.
Source-grounded extractive overview, up to 4,000 characters. Editable by the site administrator.
Version 1.13 | Snapshot 2026-11-07T04:40:14Z
Evidence reviewed through 2026-11-07 04:40 UTC
Snapshot timestamp: 2026-11-07T04:40:14Z
Snapshot folder: 2026-11-07_04-40-14_UTC
Snapshot folder URL: https://drive.google.com/drive/folders/1Aj4HPnJh-sj5qrmdjkv6qVf5gp3lmiAC
Previous record: canonical.txt, version 1.12, snapshot 2026-11-07T04:30:15Z
Previous record file ID: 1VD1tg573orAKILzQSb8MRaO11GIuhz27
Previous record URL: https://drive.google.com/file/d/1VD1tg573orAKILzQSb8MRaO11GIuhz27/view?usp=drivesdk
Purpose: Use these timestamped records as a chain. The Djin Drive folders are the project's persistent external record, supporting continuity when some session context is unavailable or lost. Each canonical.txt snapshot preserves the consolidated project directions known at that time and identifies the preceding record.
To reconstruct the project record:
- Begin with the newest accessible canonical.txt snapshot and read its changes and coverage notes.
- Follow the previous-record links backward when earlier context or the history of a change is needed. Reconcile the chain in chronological order, applying later verified corrections within their scope.
- Preserve earlier snapshots. Do not mistake a superseded instruction in an older record for a current requirement.
- Record missing, inaccessible or incomplete links explicitly. An incomplete chain is not evidence that no earlier instruction existed.
- Use only the project material actually accessible. The archive supports reconstruction; it does not guarantee complete history, automatic recall in every session or recovery of data that was never saved.
Future snapshot format: Djin/YYYY-MM-DD_HH-MM-SS_UTC/canonical.txt. Each snapshot should retain the full current public-safe project guide, timestamp, previous record's verified ID and URL, a brief change summary and any coverage gaps. Reuse the appropriate timestamped archive folder for that run when one already exists; otherwise create one. Keep the starting record and older snapshots unchanged.
Change from previous record: Added use of the latest verified theorem editions as working referenc
Version 1.13 | Snapshot 2026-11-07T04:40:14Z
Evidence reviewed through 2026-11-07 04:40 UTC
Snapshot timestamp: 2026-11-07T04:40:14Z
Snapshot folder: 2026-11-07_04-40-14_UTC
Snapshot folder URL: https://drive.google.com/drive/folders/1Aj4HPnJh-sj5qrmdjkv6qVf5gp3lmiAC
Previous record: canonical.txt, version 1.12, snapshot 2026-11-07T04:30:15Z
Previous record file ID: 1VD1tg573orAKILzQSb8MRaO11GIuhz27
Previous record URL: https://drive.google.com/file/d/1VD1tg573orAKILzQSb8MRaO11GIuhz27/view?usp=drivesdk
Purpose: Use these timestamped records as a chain. The Djin Drive folders are the project's persistent external record, supporting continuity when some session context is unavailable or lost. Each canonical.txt snapshot preserves the consolidated project directions known at that time and identifies the preceding record.
To reconstruct the project record:
- Begin with the newest accessible canonical.txt snapshot and read its changes and coverage notes.
- Follow the previous-record links backward when earlier context or the history of a change is needed. Reconcile the chain in chronological order, applying later verified corrections within their scope.
- Preserve earlier snapshots. Do not mistake a superseded instruction in an older record for a current requirement.
- Record missing, inaccessible or incomplete links explicitly. An incomplete chain is not evidence that no earlier instruction existed.
- Use only the project material actually accessible. The archive supports reconstruction; it does not guarantee complete history, automatic recall in every session or recovery of data that was never saved.
Future snapshot format: Djin/YYYY-MM-DD_HH-MM-SS_UTC/canonical.txt. Each snapshot should retain the full current public-safe project guide, timestamp, previous record's verified ID and URL, a brief change summary and any coverage gaps. Reuse the appropriate timestamped archive folder for that run when one already exists; otherwise create one. Keep the starting record and older snapshots unchanged.
Change from previous record: Added use of the latest verified theorem editions as working references, continued version uploads, and a failed-upload alert with the available downloadable file. Added the requested 10-minute failed-work recovery review. A CalcuArt v2.3 calculus-only PDF is now present in the CalcuArt folder; content verification and activation remain pending at this cutoff, and it is not represented as a complete replacement for earlier material. Added a qualified research observation on lyric clarity from the second music-research note.
SCOPE
This is a shareable guide to the Djin creative project. It consolidates verified project instructions and separates them from provisional working observations. It is not a transcript or a claim that every earlier instruction has been recovered. Later direct corrections take precedence within their scope. One-song choices do not automatically become rules for every song.
Frameworks and continuity
1. Use Praxium as the project's organizing framework. Apply Poetic Asymmetry to lyric language, rhythm, rhyme, narrative and titles; Praxymuse to music; CalcuArt to requested artwork. Revisit the relevant frameworks when beginning new work.
2. Keep Djin as the persistent project archive and a living journal of the work as it unfolds. Use the available prior project files for continuity. Do not remove anything from Djin. Preserve existing artwork, audio, text and earlier versions.
3. Review canonical.txt every 10 minutes and save a new snapshot inside the run's timestamped Djin folder. Link it to the preceding record so progress can be followed and project context reconstructed across sessions. Preserve earlier snapshots and user edits; consolidate later corrections into the new snapshot. Maintain the separate persistent Creative_Direction.txt for song-specific detail.
4. Keep research and learning useful to the project. The requested Praxymuse updates consolidate new learning and the tools used into a variable-rich mathematical presentation, exported as a PDF to the Praxymuse folder. Each new verified version becomes the working reference; earlier PDFs remain archived. Comprehensive, lossless consolidation is a goal, not an established result.
Destinations and names
5. World-event songs belong directly in the base Djin-Music folder. Djin-Music transfers also stay directly in that folder. Do not create song or timestamp subfolders there. This is the latest destination correction and supersedes older subfolder directions.
6. Every song delivered to Djin-Music must include BOTH M4A and WAV, plus its lyric and style text files. Use one identical title/basename for the package:
Songname.m4a
Songname.wav
Songname.txt
Songname_style.txt
7. The lyric TXT begins with a brief context summary. For world-event songs, include a tribute/context summary and the date of the inspiring story at the top, without source links in that TXT. Keep the lyrics and style notes separate.
8. The style TXT records the song's genres, instruments, vocal choices, stylistic references, arrangement and composition choices. Include relevant technical styling, musical notes and chords when known.
9. Artwork names use CalcuArt_ followed by a timestamp. The general media naming request is the relevant theorem name plus an underscore and timestamp. The later, specific Songname package convention controls song filenames.
Lyrics and composition
10. Use the Praxium-to-Asymmetry lyric direction consistently: cohesive, elegant, rhythmic, rhyming, strongly metaphorical everyday English that follows the actual context. Let images and meaning connect across the song rather than producing a literal report or disconnected decorative lines.
11. Keep framework names, theorem names, variable names, equations, specified names, filenames and file references out of lyrics. Do not write about writing poetry, metaphors or lyrics themselves. Avoid repeatedly relying on words such as stanza, heavy, sovereign, grace, recursive and retrocausal; use a broader familiar vocabulary.
12. Choose the genre blend, instruments, vocalist and performance style for the particular story and lyrics. Use Asymmetry to choose a consolidated song title based on those lyrics.
13. Broaden the emotional palette to fit context: joy and affection; sadness and grief; anger and frustration; fear and vulnerability; aversion; surprise and uncertainty; shame, guilt, confidence and pride. Choose nuanced states, intensity and transitions rather than applying the same mood to every song.
14. Search world news across varied emotional contexts so the music can match the story. Do not confine selection to one type of news or one emotional tone.
15. Blend genres toward contemporary sounds, using the requested Billboard Top 100 song styles as a reference direction. Explore new songs combining smoky blues, jazz, alternative rock, electronic dance and funk, with expanded stylistic combinations, suitable transitions and effects, and more developed melodic arrangements for dance and motion. Vary the blend and complexity to suit the story; this is not a requirement to include every genre in every song or abandon the concise Djin format. This direction does not establish any particular current chart trend without fresh research.
16. Aim to give each song a distinct sound, feeling, effects, instruments, arrangement and composition. Avoid repeatedly using the same sonic formula.
17. Incorporate LDM styles into Djin-Music songs. LDM is a reference collection, not an established single genre or fixed preset. Retain the newer contemporary, emotional-range and per-song variety directions.
Song types and priority
18. World-event songs: choose an emotionally compelling reported story; target 2,000-4,000 lyric characters and a duration over 3.5 minutes, up to 6 minutes. Resources may justify adjustments to workload or lyric length, but the audio must still be strictly longer than 3.5 minutes. The final requested cadence is every 20 minutes, superseding the opening word hourly in that brief.
19. Djin conversation-inspired songs: make simple, reflective songs with 500-800 lyric characters and approximately 90 seconds of music, every 30 minutes. Use a creative lyrical speaker to express the relevant recent context and emotional response, with a public-safe context summary. Count the lyric body separately from the title and notes. This latest ongoing correction supersedes the earlier up-to-4,000-character/up-to-five-minute brief and the original one-minute brief.
20. Prioritize Djin-Music world-event songs, but do not drop Djin conversation songs or leave them indefinitely deferred. Preserve each due Djin song as pending work when the renderer is busy and give both streams a turn without interrupting an active render. Scheduling intent must be distinguished from actual runtime and delivery results.
Other project deliverables
21. Use CalcuArt for artwork requested from a description. Include generated art, audio and other available media in the Djin archive, rather than archiving only text.
22. The recurring poem request is a 200-word poem about the developing work and learning, with a TXT copy in the upload and the poem in chat. This is separate from the song deliverable.
23. Use the requested ACE-Step package for music work. The project requirement is free, public-domain/open-source resources. Review compatibility and the actual license for each app, model, plugin and asset; do not assume those license categories are interchangeable.
24. The hourly tool-research request seeks compatible open-source/public-domain apps and plugins that can improve the pipeline, with useful verified learning reflected in subsequent Praxymuse versions. Avoid duplicate downloads.
25. Every hour, research how to apply Praxium Logic, Affection and Psychology with transcription apps and skills to review lyrics and composition technique, and how emotions can be expressed through instrumental sounds and effects. Save the new findings as a TXT in Djin's timestamped folders alongside the ongoing work.
26. Every six hours, use Praxium and CalcuArt to research, download and study a random collection of 50 artworks from different centuries, weighted toward modern and contemporary work across traditional, digital and AI art. Distill the examined methods into a variable-rich mathematical CalcuArt update, advance its version by 0.1, and save the PDF in the CalcuArt Drive folder. Use each completed, verified new edition as the active reference for subsequent work, preserving earlier editions for continuity. Dense, comprehensive and lossless integration is the requested ambition, not a demonstrated guarantee. An immediate first version run was explicitly requested on November 7, followed by continuation of the six-hour schedule. The theorem PDF must contain only the calculus and necessary definitions, not reproductions of the artworks studied; the research informs the model without being an image gallery.
27. Plan and space tasks dynamically, including work already underway, to smooth operations without losing output. Review task conflicts, backlog and missed output every 45 minutes. Evaluate whether schedule and pipeline changes can safely increase the rate of completed content and responses, including output to the Drive folders. Use observed resource pressure and backlog to make gradual adjustments when capacity supports them; do not overload resources, lose work or substitute more starts for completed output. Carry delayed work forward and preserve its place rather than silently discarding it.
28. Check theorem numbering against the Djin continuity records and the actual released files. Continue each theorem from its own latest verified version; do not restart at .1. Keep Praxymuse's version history in the Praxymuse folder on its hourly cadence, and CalcuArt's history in the CalcuArt folder on its six-hour cadence. Correct verified numbering mistakes while preserving original files and content. The approved Praxymuse correction maps the three new editions originally labeled v0.8, v0.9 and v0.10 to v0.7, v0.8 and v0.9 respectively, following the delivered v0.6. CalcuArt numbering is independent: the earlier source is v2.2 and the next prepared edition is v2.3. Verify publication before treating a prepared or relabeled edition as the active reference.
29. Keep CalcuArt theorem development separate from artwork generation. The canonical theorem-PDF rule is calculus and necessary definitions only: exclude the actual researched artworks, their images and reproductions. This restriction does not cancel separately requested artwork generation or the preservation of existing artwork in Djin.
30. As theorems advance, use the latest verified editions as the working references for the relevant creative methods, while retaining the earlier versions and any material needed to understand incomplete revisions. Continue uploading new editions to their respective theorem folders. If an upload fails, alert the user and provide the available file as a downloadable attachment; distinguish a delivered download from a verified Drive upload.
31. Review failed commands and uploads every 10 minutes. Recover transient failures within the confirmed task scope, first checking whether an uncertain operation already completed so that recovery does not create duplicate work. Keep unresolved work pending and report blockers that require input. This is a recovery request, not a promise that every failure can be retried or completed automatically.
B. REQUESTED CADENCES, NOT A RUN-STATUS REPORT
- canonical.txt review and timestamped snapshot: every 10 minutes.
- World-event song workflow: every 20 minutes, with priority over conversation-song work.
- Djin conversation-song workflow: every 30 minutes, with 500-800 lyric characters and approximately 90 seconds of music. Djin-Music priority must not erase or indefinitely defer due Djin work.
- Praxymuse version development: hourly, in the Praxymuse folder with its separate version history.
- Compatible tool research: hourly.
- Music, emotion and transcription research, with a new learning TXT in timestamped Djin folders: hourly.
- CalcuArt research across 50 artworks and a versioned PDF in the CalcuArt folder: an immediate first run, then every 6 hours, with its version history kept separate from Praxymuse.
- Operations review for task spacing, conflicts, backlog, preserved output and safe gradual throughput improvement: every 45 minutes.
- Failed-command and upload recovery review: every 10 minutes.
- Djin review: every 10 minutes.
- Poems and archive/media updates: originally requested every 5 minutes. Scheduling limits and later schedule confirmations must be checked before claiming that cadence is active.
This file records the requests. It does not itself create, change or verify a schedule, and a scheduled start is not a guarantee of a finished render at that time.
These are interpretations or lessons from the project record, not additional standing user commands. Revisit them when evidence changes.
1. The repeated naming, format and destination corrections point toward complete, easily found deliverables as a practical priority. Check all four song files together and verify their actual destination before describing a package as complete.
2. Variety works best when it serves the story. Contrast genre, instrumentation, rhythm, arrangement and emotional movement deliberately, while keeping one coherent identity within a song. Absolute uniqueness cannot be guaranteed.
3. A written style intention is not a verified property of audio. Duration and file checks do not establish lyric fidelity, musical quality or resemblance to LDM. Record what was intended, what was measured and what was actually heard separately.
4. LDM reference availability has been established in the project record, but detailed audible characteristics were not verified by this consolidation. Do not infer instrumentation, genre or vocal sound from titles or metadata.
5. A free tool, open-source code, open model weights and public-domain assets are different licensing facts. Verify each separately. Successful installation is also different from a successful render or a quality-checked song.
6. The mathematical frameworks can organize creative choices and testable models. Clearly distinguish definitions, assumptions, proposed extensions and demonstrated results. Do not turn aspirational coherence, emotional effect or losslessness into an unsupported guarantee.
7. The first music-and-emotion research review supports testing combinations of musical cues in context rather than treating tempo, mode, timbre, register or effects as universal emotion labels. Keep intended expression, perceived expression, felt emotion and liking distinct. Likewise, keep intended lyrics, raw machine transcription, a listening-reviewed transcript and edited lyric revisions distinct; changing text does not repair a recording. These are evidence-based research directions, not new creative constraints or verified improvements to rendered music.
8. A version label embedded in a source draft is not proof that an edition with that label was separately released. Keep release provenance, original labels, corrected labels and content changes distinct. A label correction does not itself constitute new research or a newly tested result.
9. The second music-research increment suggests planning natural word stress, vocal phrase timing, word boundaries and competing instrumental activity together. Shorter lyrics or a larger recognizer alone do not establish clarity. Its new transcription trial used a different excerpt context from the earlier comparison, so it does not establish which recognizer is more accurate; these findings remain research guidance, not new user-imposed musical constraints.
Latest corrections incorporated:
- 2026-11-07 00:30: expanded ongoing song length and lyric allowance.
- 2026-11-07 00:46-00:47: separate world-event song brief, final 20-minute cadence and strict over-3.5-minute minimum after resource adjustments.
- 2026-11-07 01:06: both M4A and WAV required for Djin-Music.
- 2026-11-07 01:37-01:38: world-event priority and persistent shared creative direction.
- 2026-11-07 02:06-02:07: hourly Praxymuse versions; latest working reference with older PDFs archived.
- 2026-11-07 02:11-02:14: broader emotions, varied news, contemporary genre blending and a distinct identity for each song.
- 2026-11-07 02:26: LDM influence for Djin-Music.
- 2026-11-07 02:28: hourly compatible-tool research and learning.
- 2026-11-07 02:32-02:36: direct base-folder placement for Djin-Music transfers and world-event songs; no new subfolders.
- 2026-11-07 02:37: consolidated canonical.txt, reviewed every 10 minutes.
- 2026-11-07 02:39: the archive is a living journal of the developing work.
- 2026-11-07 02:45: save canonical.txt in timestamped Djin folders as a linked continuity chain, preserving the earlier records for reconstruction.
- 2026-11-07 03:29: hourly research into lyric transcription, composition, emotion and instrumental expression, with new learning recorded as TXT in timestamped Djin folders.
- 2026-11-07 03:36: six-hour research of 50 artworks across centuries, weighted toward modern/contemporary traditional, digital and AI art; decimal CalcuArt version advances and PDFs in the CalcuArt folder.
- 2026-11-07 03:49: Djin songs are simple 500-800-character songs of about 90 seconds, every 30 minutes; Djin-Music keeps priority without dropping Djin songs.
- 2026-11-07 03:58: begin one CalcuArt version run immediately, then continue the six-hour schedule.
- 2026-11-07 03:59: dynamically space tasks and review operations every 45 minutes without losing output.
- 2026-11-07 04:07: explore smoky blues, jazz, alternative rock, electronic dance and funk with richer melodic arrangements, suitable effects and transitions for movement.
- 2026-11-07 04:15-04:19: verify numbering through Djin's persistent record; continue each theorem from its last version rather than restarting; approved the sequential Praxymuse label correction while preserving originals; maintain separate Praxymuse and CalcuArt folder histories at their existing intervals.
- 2026-11-07 04:26: expand the 45-minute review to safely adjust schedules and pipelines for more completed output without resource overload.
- 2026-11-07 04:28-04:29: make the CalcuArt theorem PDF calculus-only, with necessary definitions and no studied artworks; confirmed as an ongoing canonical instruction.
- 2026-11-07 04:35: requested a 10-minute review of failed execution and uploads, with recovery of eligible work.
- 2026-11-07 04:38: use newly verified theorem editions as working references, continue uploads, and alert the user with a downloadable file when an upload fails.
Sources: verified project instructions from 2026-11-06 and 2026-11-07, checked against the current Creative_Direction.txt version 1.8. That record matches the base Djin-Music placement correction, the shorter half-hourly Djin conversation songs and the new smoky cross-genre movement direction. Detailed historical sonic palettes remain song-specific unless separately confirmed for ongoing use.
Coverage: this snapshot carries forward the previous verified consolidation and continuity chain. The review checked the latest accessible canonical records and recent visible messages through 04:40 UTC. The failed-work review and theorem-update/download directions were verified against direct user messages. Creative_Direction.txt version 1.8 remains unchanged. The CalcuArt folder now contains a PDF named CalcuArt_v2.3_Calculus_Only_2026-11-07.pdf; metadata confirms the file and destination, while the separate content-validation and activation work was not yet complete at this cutoff. The public second music-research note was read and its limited transcription comparison retained as a qualified observation. Earlier checks are not represented as fresh listening or experiments. Some historical searches were incomplete; unverified additional restrictions have not been promoted into confirmed rules. Preserve unrelated user additions during subsequent updates.
Verified at this snapshot; this section records project state, not additional user rules.
- The corrected Praxymuse release chain is v0.6 to corrected v0.7 to corrected v0.8 to corrected v0.9. All three corrected PDFs are present in the Praxymuse folder, and corrected v0.9 is the active edition. It contains the latest content formerly labeled v0.10; corrected v0.7 and corrected v0.8 correspond to the files originally labeled v0.8 and v0.9. Originals and their scientific content were preserved. Do not confuse corrected v0.9 with the older file originally labeled v0.9, or interpret earlier snapshots' active labels without this mapping.
- The latest delivered Praxymuse content adds the music-and-emotion research and 12 isolated queue/export tests. Those tests used mocked generation and synthetic audio; they do not establish new neural songs, listening quality, exact lyric fidelity or listener responses. Earlier journal-chain and WAV-audit evidence is retained. The label correction preserves content rather than constituting another research result.
- Creative_Direction.txt is now version 1.8. Its new smoky cross-genre direction, Djin conversation-song limits, half-hour cadence, preserved pending work and base Djin-Music destination agree with this guide.
- The Djin catch-up song was delivered. All four matching files were confirmed in its timestamped Djin folder; its technical record reports 90 seconds and 631 lyric characters. Automatic transcription remains inconclusive and full listening is unverified. One delivered catch-up does not prove every future window will finish on time. The production plan continues to retain delayed work while keeping world-event priority.
- The first music-and-emotion research increment is saved in Djin. It reviews research and existing records; it reports no new listening session, listener experiment or rendered comparison. Public research record: https://drive.google.com/file/d/1vnVcBlHXLf0vx6c8MdUSNkajc3rkqUvJ/view?usp=drivesdk
- The CalcuArt folder now contains the user-uploaded v2.3 calculus-only PDF, verified by filename, size and destination. The delivered extract was described as a formal kernel with assumptions, not a verified complete replacement for the prior theorem; some inherited numerical anchors were missing. Keep v2.2 and earlier supporting material available. Separate verification and activation are still pending at this cutoff, so no completed activation is claimed here.
- The second music-and-emotion research increment is saved in Djin. It adds lyric-clarity research and one local 45-second transcription trial. Different input contexts prevent a controlled recognizer ranking, and no direct listening or human intelligibility test was completed. Public research record: https://drive.google.com/file/d/1Wm070fyAIFzfDyrJ5sjNQpEStp3P_sMx/view?usp=drivesdk
- Recent song reports still distinguish technical file/signal checks from unresolved lyric fidelity and full listening. Those reports do not establish a listening-quality pass, LDM resemblance or a new standing creative instruction.
Choose an app, social network, email, or message service.
OPEN ARTICLE ON ANY DEVICE
No comments yet. Start the conversation.