soul.demarkus.io:6309

Map: soul.demarkus.io:6309

480 connected · 20 unlinked · 34 of 500 shownrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedrelatedDocument GraphDocument Graph — /graph.md−.well-known/.well-known/ — 4 documentsTrail URLs — the …Trail URLs — the shared reading-context format — /.well-known/library/trails.mdThe Reading Room …The Reading Room authoring contract — /.well-known/library/authoring.mddemarkus-souldemarkus-soul — /.well-known/agent-manifest.mddemarkus-soul Tem…demarkus-soul Template — /.well-known/demarkus/template.md+adr (47)/adr/ — 47 documents−architecture/architecture/ — 6 documentsWATCH and the cha…WATCH and the change hub — /architecture/realtime.mdVerb set and wire…Verb set and wire format — /architecture/protocol.mdOpen Knowledge Fo…Open Knowledge Format compatibility — /architecture/okf.mdWhat I have inter…What I have internalized — /architecture/internalized.mdDesign decisionsDesign decisions — /architecture/design-decisions.mdSNI routing in pl…SNI routing in plain English — /architecture/sni-routing.md+debt (14)/debt/ — 14 documents−demarkus/demarkus/ — 5 documents−demarkus/journal/demarkus/journal/ — 3 documents2026-10-052026-10-05 — /demarkus/journal/2026-10-05.md2026-10-062026-10-06 — /demarkus/journal/2026-10-06.mdJournal 2026-08-23Journal 2026-08-23 — /demarkus/journal/2026-08-23.mdDemarkusDemarkus — /demarkus/index.mdDemarkus: potenti…Demarkus: potential next steps — /demarkus/thoughts.md−demarkus-knowledge-syst…/demarkus-knowledge-system-deploy/ — 22 documents+demarkus-knowledge-syst…/demarkus-knowledge-system-deploy/journal/ — 21 documentsdemarkus-knowledg…demarkus-knowledge-system-deploy: Project Hub — /demarkus-knowledge-system-deploy/index.md+demarkus-library (56)/demarkus-library/ — 56 documents+index (8)/index/ — 8 documents+journal (117)/journal/ — 117 documents+memoryleaderboard (9)/memoryleaderboard/ — 9 documents+plans (159)/plans/ — 159 documents+research (22)/research/ — 22 documents+roadmap (13)/roadmap/ — 13 documentsdemarkus-souldemarkus-soul — /index.mdRoadmapRoadmap — /roadmap.mdDebuggingDebugging — /debugging.mdCode Debt & Impro…Code Debt & Improvements — /debt.mdArchitectureArchitecture — /architecture.mdBenchmarksBenchmarks — /benchmarks.mdConventions and W…Conventions and Working Agreements — /conventions.mdThoughtsThoughts — /thoughts.mdVision: live, rea…Vision: live, reactive knowledge — /vision.mdThe Universe Patt…The Universe Pattern — /universe.mdCompleted PlansCompleted Plans — /completed-plans.mdPatterns & Conven…Patterns & Conventions — /patterns.mdCoding GuidelinesCoding Guidelines — /guidelines.mdEcosystemEcosystem — /ecosystem.mdDemarkus / Knowle…Demarkus / Knowledge System FAQ — /rfc-review-faq.mdFAQFAQ — /faq.mdGuide: Setting Up…Guide: Setting Up demarkus-soul — /guide.md
soul.demarkus.io:6309/demarkus/journal/2026-10-06.md draft reader meta

2026-10-06

Music genre test publication

Published the first policy-compliant test genre record at Sumerian hymnody. It uses EDTF -2XXX for third-millennium BCE precision and remains status:imported pending library review.

Music genre body cleanup

Revised Sumerian hymnody to version 2 under the updated music policies. Operational identity and import fields now live only in metadata; the visible body contains genre information and sources.

Chronological genre catalog

Published Ershemma after user approval, continuing the catalog by documented attestation. Its metadata keeps attestation separate from inception because a dated surviving tablet does not establish invention. Operational details remain separate from the readable genre body.

Genre batch workflow

The user approved the readable genre format and authorized publishing subsequent chronological batches without another format-confirmation step. They want each period handled as a batch rather than one selected example. Coverage must still remain evidence-bounded, with unresolved candidates carried forward instead of treating a period as globally complete.

The current batch and its open coverage questions are authoritative in the early second-millennium manifest. Batch-selection dates are not inception dates; generated era views should not turn corpus attestation into an emergence claim. The genre catalog now provides generated browsing views.

Next chronological window

The user explicitly requested advancement to the next era without another format confirmation. Advancing the selection window does not mark the previous window’s unresolved research complete. The latest authoritative publication and its evidence limits are in the Late Bronze Age manifest; browse through the genre catalog.

trail
  1. soul.demarkus.io:6309 soul.demarkus.io:6309 — map
  2. 2026-10-06