{ "title": "The twelve Processor modules, in practice — Tools & experiences", "text": "MODAVIS (2026). The twelve Processor modules, in practice — Tools & experiences. Research notebooks, September 2026 · Connected evidence edition. https://modavis.org/editions/2026-09-r6/software/modules/", "bibtex": "@misc{modavis_software_modules_2026_09_r6,\n author = {{MODAVIS}},\n title = {The twelve Processor modules, in practice — Tools & experiences},\n year = {2026},\n month = {09},\n version = {2026-09-r6},\n url = {https://modavis.org/editions/2026-09-r6/software/modules/},\n note = {Content SHA-256: a96f1826794fa4861dfb0f6309c0423459d3453639bff4943be801038fb3d67e}\n}", "url": "https://modavis.org/editions/2026-09-r6/software/modules/", "sha256": "a96f1826794fa4861dfb0f6309c0423459d3453639bff4943be801038fb3d67e", "edition": "2026-09-r6", "date": "2026-09-26", "canonicalPayload": "{\"book\":{\"number\":\"06\",\"slug\":\"software\",\"title\":\"Tools & experiences\"},\"chapter\":{\"blocks\":[{\"id\":\"module-contracts\",\"text\":\"Follow the input, output and review boundary\",\"type\":\"heading\"},{\"text\":\"The current module guide describes twelve modules in Processor 0.2.0, an unpublished development candidate. The following map explains those documented responsibilities. It is not an assertion that each module is independently released, broadly benchmarked or available through a public service. Choose a module by the material it accepts and the evidence it returns, then preserve the review decision that connects its result to the research record.\",\"type\":\"p\"},{\"headers\":[\"Module\",\"Input → output\",\"Interpretation and review\"],\"rows\":[[\"Ingestor\",\"Registered transfer records → source-preserving staging records.\",\"Schema-valid staging establishes an intake contract; it does not make the content an accepted canonical fact.\"],[\"Normalizer\",\"Staged source records → deterministic normalized candidates with original evidence.\",\"Review and projection remain explicit. Exact replay preserves existing decisions instead of silently replacing them.\"],[\"Bootstrap\",\"Versioned policies, observations and decisions → governed projection receipts.\",\"Projection depends on the authorized policy and its prerequisites; it is not unrestricted automatic acceptance.\"],[\"Document evidence\",\"Identified document bytes → pages, assets, exact selectors and candidate assertions.\",\"A quotation must resolve to its source. Silence or an absent value must not become an invented numerical fact.\"],[\"Localizer\",\"Place mentions and provider evidence → ranked geographic candidates.\",\"Retain ambiguity, temporal context and unknown positional accuracy. A high-ranked candidate is not automatically the historical location.\"],[\"Language detection\",\"Source text → language-identification evidence for quality review.\",\"Short or ambiguous text can justify abstention. Uncalibrated scores are not probabilities of correctness.\"],[\"Litparser\",\"Citation strings → literature candidates with literal field evidence.\",\"Conflicting years and indefinite page continuations remain uncertain; parsing does not authorize a canonical bibliographic write.\"],[\"Enrichment\",\"An authorized page or workflow → retained institution or virtual-instrument facts.\",\"Fetching is opt-in and source-bound. Replaying retained evidence is distinct from obtaining a new page snapshot.\"],[\"PLENUM\",\"Claim-scoped evidence → versioned suitability and source-dependence assessments.\",\"The result is a policy-based assessment for a claim, not permanent trust in a publisher or a truth probability.\"],[\"Ambitus\",\"MusicXML, compressed MXL or MIDI → nominal pitch-range evidence.\",\"Instrument identity remains a separate question. MIDI pitch-control information is flagged rather than silently treated as measured acoustic pitch.\"],[\"Imageseg\",\"Image and SAM 2 configuration → aligned masks and annotations.\",\"Masks are class-agnostic. A selected region needs interpretation and review before it becomes an organological component label.\"],[\"Modelgenerator\",\"Photographic bundle and pinned DA3 configuration → checked point clouds and camera paths.\",\"These are not automatically textured meshes. Registration, visibility and transport verification are separate concerns.\"]],\"type\":\"table\"},{\"id\":\"a-document-path\",\"text\":\"Example: a historical account becomes a candidate\",\"type\":\"heading\"},{\"text\":\"Consider a supplied document naming a workshop, place and construction year. Intake preserves the source identity. Document evidence identifies the relevant page and passage. Language detection and Litparser can assist interpretation or bibliography; Localizer can propose geographic matches. Normalizer organizes candidate values without discarding the literal account. PLENUM evaluates how suitable that account is for the particular proposition and whether other accounts depend on it.\",\"type\":\"p\"},{\"text\":\"The editorial question is then precise: does the passage support construction by this workshop for this instrument state and date? A page mentioning a workshop nearby, or a contract that did not lead to completion, requires a different relation. The accepted projection should retain the reviewed claim and its grounds. If the evidence is insufficient, preserving an unresolved candidate is more informative than forcing a clean but unsupported value.\",\"type\":\"p\"},{\"boundary\":\"The example illustrates component responsibilities without attributing unverified processing history to the actual release.\",\"caseLabel\":\"Cuntz\",\"concept\":\"A processing candidate is a proposed interpretation of source material. Review and publication are additional decisions, with their own evidence and responsibilities.\",\"evidence\":\"Illustrative scenario\",\"expanded\":false,\"id\":\"cuntz-software-boundaries\",\"scenario\":\"Use the Cuntz workbook observation to imagine a new import workflow. This is an explanatory mapping to the Processor architecture, not a claim that the published Cuntz release was built by all current Processor modules.\",\"sources\":[{\"detail\":\"Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.\",\"href\":\"https://doi.org/10.5281/zenodo.22151203\",\"label\":\"Cuntz Positiv · VAO 0.5.0-rc.2\"},{\"detail\":\"Identity, state, configuration, evidence, assertions, context and provenance. Teaching examples explain its distinctions without inventing new normative properties.\",\"href\":\"https://doi.org/10.5281/zenodo.22126086\",\"label\":\"MODAVIS Ontology Network 0.1.0\"}],\"steps\":[{\"text\":\"Intake identifies the workbook bytes and source context. Extraction retains the literal cell, property code and unit rather than keeping only a convenient normalized number.\",\"title\":\"Preserve the source\"},{\"text\":\"A normalizer can propose a structured observation and a pipe identity. A reviewer checks the cell interpretation, the identity match and qualifications such as the timestamp note.\",\"title\":\"Inspect the candidate\"},{\"text\":\"An accepted projection keeps the evidence link and decision. A public view can be concise while a fixed release preserves the record needed to re-examine the claim.\",\"title\":\"Publish the accountable result\"}],\"takeaway\":\"Automation can propose a useful structure; an accountable workflow keeps the interpretation and its grounds inspectable.\",\"title\":\"Where does an extracted number become an accepted claim?\",\"type\":\"example\"},{\"id\":\"a-media-path\",\"text\":\"Example: images and scores support different claims\",\"type\":\"heading\"},{\"text\":\"Imageseg can isolate a visible region for inspection; Modelgenerator can estimate spatial structure from a photographic bundle. Neither establishes the identity or date of the object pictured. Ambitus can describe the nominal range of a score or MIDI file; it does not establish that a particular surviving instrument can produce every encoded pitch under its current configuration. Connect each derived asset to its source and the domain question it actually addresses.\",\"type\":\"p\"},{\"id\":\"diagnostics\",\"text\":\"Use diagnostics to answer a bounded question\",\"type\":\"heading\"},{\"label\":\"Processor source checkout · documented local inspection commands\",\"text\":\"modavis-processor modules --check-imports\\nmodavis-processor example\",\"type\":\"code\"},{\"text\":\"In the documented development package, the first command inspects the module inventory and imports; the second runs an authored, deterministic PLENUM example without requiring a database, model or service. It reports the modavis.plenum.v1 policy with automatic promotion disabled. These checks help establish that a local installation and example behave as described. They do not evaluate extraction accuracy over a historical corpus or validate an external provider.\",\"type\":\"p\"},{\"text\":\"For a meaningful module evaluation, retain the diagnostic input, expected task, actual output and failure cases. Separate transport success from semantic correctness, model availability from useful output, and a small authored fixture from a representative benchmark. The module guide’s boundaries are especially useful here: they show where an automated result stops and a research judgment begins.\",\"type\":\"p\"},{\"items\":[{\"detail\":\"All components, modules, experiences and supporting resources.\",\"href\":\"/notebooks/software/directory/\",\"label\":\"The full ecosystem directory\"},{\"detail\":\"Which tool produces which kind of model.\",\"href\":\"/notebooks/software/reconstruction/\",\"label\":\"Geometry and acoustic reconstruction\"}],\"type\":\"links\"}],\"intro\":\"Processor modules turn acquired material into inspectable candidates and derived assets. Their outputs have different evidential roles; none should be treated as a general-purpose authority on an instrument.\",\"slug\":\"modules\",\"sources\":[{\"detail\":\"Project documentation inspected on 26 September 2026; package 0.2.0, an unpublished development candidate. Used for current module responsibilities and limitations, not as a claim of public package availability.\",\"label\":\"MODAVIS Processor · module guide and package README\"},{\"detail\":\"Project component documentation inspected on 26 September 2026. Used for the division of responsibilities among Initiator, Aggregator, Processor, Navigator, Prospector, Persistor and supporting services.\",\"label\":\"MODAVIS Framework · component registry\"},{\"detail\":\"A separately archived demonstration resource; not a substitute for the current unpublished Processor package.\",\"href\":\"https://doi.org/10.5281/zenodo.22662664\",\"label\":\"Research workflow demonstrations 0.1.1\"},{\"detail\":\"Dissertation submitted to Universität Leipzig, 11 September 2026. Chapter 4 on source processing and provenance; §8.3.4.1 on claim-scoped assessment. Page numbers refer to the printed manuscript pagination. The manuscript is not distributed by this website.\",\"label\":\"Dominik Ukolov · Musikinstrumente im virtuellen Raum (2026)\"}],\"title\":\"The twelve Processor modules, in practice\"},\"date\":\"2026-09-26\",\"edition\":\"2026-09-r6\",\"figures\":{}}", "payload": { "edition": "2026-09-r6", "date": "2026-09-26", "book": { "slug": "software", "title": "Tools & experiences", "number": "06" }, "chapter": { "slug": "modules", "title": "The twelve Processor modules, in practice", "intro": "Processor modules turn acquired material into inspectable candidates and derived assets. Their outputs have different evidential roles; none should be treated as a general-purpose authority on an instrument.", "blocks": [ { "type": "heading", "id": "module-contracts", "text": "Follow the input, output and review boundary" }, { "type": "p", "text": "The current module guide describes twelve modules in Processor 0.2.0, an unpublished development candidate. The following map explains those documented responsibilities. It is not an assertion that each module is independently released, broadly benchmarked or available through a public service. Choose a module by the material it accepts and the evidence it returns, then preserve the review decision that connects its result to the research record." }, { "type": "table", "headers": [ "Module", "Input → output", "Interpretation and review" ], "rows": [ [ "Ingestor", "Registered transfer records → source-preserving staging records.", "Schema-valid staging establishes an intake contract; it does not make the content an accepted canonical fact." ], [ "Normalizer", "Staged source records → deterministic normalized candidates with original evidence.", "Review and projection remain explicit. Exact replay preserves existing decisions instead of silently replacing them." ], [ "Bootstrap", "Versioned policies, observations and decisions → governed projection receipts.", "Projection depends on the authorized policy and its prerequisites; it is not unrestricted automatic acceptance." ], [ "Document evidence", "Identified document bytes → pages, assets, exact selectors and candidate assertions.", "A quotation must resolve to its source. Silence or an absent value must not become an invented numerical fact." ], [ "Localizer", "Place mentions and provider evidence → ranked geographic candidates.", "Retain ambiguity, temporal context and unknown positional accuracy. A high-ranked candidate is not automatically the historical location." ], [ "Language detection", "Source text → language-identification evidence for quality review.", "Short or ambiguous text can justify abstention. Uncalibrated scores are not probabilities of correctness." ], [ "Litparser", "Citation strings → literature candidates with literal field evidence.", "Conflicting years and indefinite page continuations remain uncertain; parsing does not authorize a canonical bibliographic write." ], [ "Enrichment", "An authorized page or workflow → retained institution or virtual-instrument facts.", "Fetching is opt-in and source-bound. Replaying retained evidence is distinct from obtaining a new page snapshot." ], [ "PLENUM", "Claim-scoped evidence → versioned suitability and source-dependence assessments.", "The result is a policy-based assessment for a claim, not permanent trust in a publisher or a truth probability." ], [ "Ambitus", "MusicXML, compressed MXL or MIDI → nominal pitch-range evidence.", "Instrument identity remains a separate question. MIDI pitch-control information is flagged rather than silently treated as measured acoustic pitch." ], [ "Imageseg", "Image and SAM 2 configuration → aligned masks and annotations.", "Masks are class-agnostic. A selected region needs interpretation and review before it becomes an organological component label." ], [ "Modelgenerator", "Photographic bundle and pinned DA3 configuration → checked point clouds and camera paths.", "These are not automatically textured meshes. Registration, visibility and transport verification are separate concerns." ] ] }, { "type": "heading", "id": "a-document-path", "text": "Example: a historical account becomes a candidate" }, { "type": "p", "text": "Consider a supplied document naming a workshop, place and construction year. Intake preserves the source identity. Document evidence identifies the relevant page and passage. Language detection and Litparser can assist interpretation or bibliography; Localizer can propose geographic matches. Normalizer organizes candidate values without discarding the literal account. PLENUM evaluates how suitable that account is for the particular proposition and whether other accounts depend on it." }, { "type": "p", "text": "The editorial question is then precise: does the passage support construction by this workshop for this instrument state and date? A page mentioning a workshop nearby, or a contract that did not lead to completion, requires a different relation. The accepted projection should retain the reviewed claim and its grounds. If the evidence is insufficient, preserving an unresolved candidate is more informative than forcing a clean but unsupported value." }, { "type": "example", "id": "cuntz-software-boundaries", "title": "Where does an extracted number become an accepted claim?", "concept": "A processing candidate is a proposed interpretation of source material. Review and publication are additional decisions, with their own evidence and responsibilities.", "scenario": "Use the Cuntz workbook observation to imagine a new import workflow. This is an explanatory mapping to the Processor architecture, not a claim that the published Cuntz release was built by all current Processor modules.", "steps": [ { "title": "Preserve the source", "text": "Intake identifies the workbook bytes and source context. Extraction retains the literal cell, property code and unit rather than keeping only a convenient normalized number." }, { "title": "Inspect the candidate", "text": "A normalizer can propose a structured observation and a pipe identity. A reviewer checks the cell interpretation, the identity match and qualifications such as the timestamp note." }, { "title": "Publish the accountable result", "text": "An accepted projection keeps the evidence link and decision. A public view can be concise while a fixed release preserves the record needed to re-examine the claim." } ], "takeaway": "Automation can propose a useful structure; an accountable workflow keeps the interpretation and its grounds inspectable.", "boundary": "The example illustrates component responsibilities without attributing unverified processing history to the actual release.", "sources": [ { "label": "Cuntz Positiv · VAO 0.5.0-rc.2", "href": "https://doi.org/10.5281/zenodo.22151203", "detail": "Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release." }, { "label": "MODAVIS Ontology Network 0.1.0", "href": "https://doi.org/10.5281/zenodo.22126086", "detail": "Identity, state, configuration, evidence, assertions, context and provenance. Teaching examples explain its distinctions without inventing new normative properties." } ], "expanded": false, "caseLabel": "Cuntz", "evidence": "Illustrative scenario" }, { "type": "heading", "id": "a-media-path", "text": "Example: images and scores support different claims" }, { "type": "p", "text": "Imageseg can isolate a visible region for inspection; Modelgenerator can estimate spatial structure from a photographic bundle. Neither establishes the identity or date of the object pictured. Ambitus can describe the nominal range of a score or MIDI file; it does not establish that a particular surviving instrument can produce every encoded pitch under its current configuration. Connect each derived asset to its source and the domain question it actually addresses." }, { "type": "heading", "id": "diagnostics", "text": "Use diagnostics to answer a bounded question" }, { "type": "code", "label": "Processor source checkout · documented local inspection commands", "text": "modavis-processor modules --check-imports\nmodavis-processor example" }, { "type": "p", "text": "In the documented development package, the first command inspects the module inventory and imports; the second runs an authored, deterministic PLENUM example without requiring a database, model or service. It reports the modavis.plenum.v1 policy with automatic promotion disabled. These checks help establish that a local installation and example behave as described. They do not evaluate extraction accuracy over a historical corpus or validate an external provider." }, { "type": "p", "text": "For a meaningful module evaluation, retain the diagnostic input, expected task, actual output and failure cases. Separate transport success from semantic correctness, model availability from useful output, and a small authored fixture from a representative benchmark. The module guide’s boundaries are especially useful here: they show where an automated result stops and a research judgment begins." }, { "type": "links", "items": [ { "label": "The full ecosystem directory", "href": "/notebooks/software/directory/", "detail": "All components, modules, experiences and supporting resources." }, { "label": "Geometry and acoustic reconstruction", "href": "/notebooks/software/reconstruction/", "detail": "Which tool produces which kind of model." } ] } ], "sources": [ { "label": "MODAVIS Processor · module guide and package README", "detail": "Project documentation inspected on 26 September 2026; package 0.2.0, an unpublished development candidate. Used for current module responsibilities and limitations, not as a claim of public package availability." }, { "label": "MODAVIS Framework · component registry", "detail": "Project component documentation inspected on 26 September 2026. Used for the division of responsibilities among Initiator, Aggregator, Processor, Navigator, Prospector, Persistor and supporting services." }, { "label": "Research workflow demonstrations 0.1.1", "href": "https://doi.org/10.5281/zenodo.22662664", "detail": "A separately archived demonstration resource; not a substitute for the current unpublished Processor package." }, { "label": "Dominik Ukolov · Musikinstrumente im virtuellen Raum (2026)", "detail": "Dissertation submitted to Universität Leipzig, 11 September 2026. Chapter 4 on source processing and provenance; §8.3.4.1 on claim-scoped assessment. Page numbers refer to the printed manuscript pagination. The manuscript is not distributed by this website." } ] }, "figures": {} } }