Morkahja — Content, Lore and Provenance
Game-content families
- Encounters and solutions: the original journal begins with LudusOccursus/LudusSolutio data organization (May 16, 2026); later implementation includes solution IDs, reward previews, encounter outcomes and expansion gating.
- Character and progression: avatars, portraits and frames, death handling, inventory, achievements, gems, rewards and unlockable expansions.
- Events and social content: SCRIBES activity feed, friends, achievement notifications, world updates and donation-related entries.
- Illustration and presentation: encounter illustrations, UI frames, backgrounds, dashboard controls, seasonal loading logos and icons.
- Audio: dashboard and in-game playlists, music controls and effects; preserve music contributor attribution.
- Supporting records: original root-level DEVLOG, source comments, tests, game data, and Git commits.
Creative provenance
Babuni.dev is the world and game project's original author and creative director. Individual imported content items should retain any separately evidenced illustrator, composer or other third-party credit. The original journal supplies dated development evidence, not a license to invent lore or to assign unrecorded writing to AI.
Portfolio publishing requirements
For each featured encounter, illustration, mechanic or worldbuilding entry, record: title, content source and path, what the visitor is seeing, evidence date or version when documented, author/contributor credits, rights and whether behavior was actually tested. Original journal entries should be summarized with links rather than replaced. Do not expose player accounts, production database data, authentication materials, private chats or credentials.
Unresolved
A full canon index, rights inventory, approved visual gallery, playable deployment status and historical authorship of individual reconstructed assets require separately sourced review.
2026-10-31 — Publication boundaries
The existing standard documentation is the project source for the future portfolio connection. See publication preparation. Preserve contributor credits, canonical-source boundaries and original journals. No private findings, live records or secret values are copied into the portfolio.
Document information
Author: Babuni.dev
Scope: Inventory of content systems from the repository and the dated original devlog. This is not a claim to have validated all files or established complete world canon.