Feature: Create space on UOR-Framework Wiki for the Academic Documentation content

[RobinWikoff]

Title: Feature: Create space on UOR-Framework Wiki for the Academic Documentation content

Summary

We (the academic documentation working group) are going to make a new space in the UOR-Framework Github Wiki for the academic documentation and written communication to be kept, in a wiki format.

Details

1. Main Wiki is here: https://github.com/UOR-Foundation/UOR-Framework/wiki
2. Alex or John needs to to make a partition that is only for Academic Documentation, that Robin authors content for, with its own URL
3. Alex or John needs to provide a process/SOP for updating content. In general Robin will submit Issues, but also consider minor edits or using a github agent within VS Code to modify, similar to Robin’s Farm Monitor wiki process.

Open Questions

• Incorporating/combining Main Wiki and Academic Documentation? At some point will need to coordinate
• Robin will provide content for the welcome/landing page that contains: Why of UOR, What of UOR, Level 1 concept map style. (separate issue)

Acceptance Criteria

• New Wiki Partition is visible on WIki
• SOP is created for updating / adding content
• Landing Page is created (content for a separate issue)

Additional context

• Kick off / group meeting on 2026-May-05
• Next meeting: every two weeks Ilya managing
• Robin will make issues to submit to github for Alex and John to do tasks about / on the wiki academic documentation part
• Wiki: https://github.com/UOR-Foundation/UOR-Framework/wiki, currently hosts Alex’s documentation, fold in / reference in Academic documentation when applicable
• Boundaries: for this project = what we need to use an Instance.

[afflom]

As per our 1:1, this will be called Scientific Methods and Results

[RobinWikoff]

Task 2: SOP discussed: Robin submits issues / requests to Alex who addresses/completes them by adding content to the Wiki Scientific Methods and Results partition. Closes Issue 2.2 (1 is not yet complete)

[RobinWikoff]

Additional/Related Subtask for Alex! Content for first page in new partition

From 1:1 discussions, I realized you do need landing page content now, I am going to make a more complete version in the near future, I will create an issue for that with content and task.

First Page / Landing Page content for now: brackets are where you fill in, the text in middle is content.

[Same heading as eg https://github.com/UOR-Foundation/UOR-Framework/wiki/01-Introduction-and-Goals, where title of page is heading title]

This documentation is to help explain What and Why and How about the UOR-Framework, PRISM-SDK, and an Instance. These terms might be updated and come directly from the Academic Conceptual Model. We will use this conceptual model to explain why someone would use UOR, what it can do, and how it does it. Then we'll go into how we know it does what we think it does (Verification) and if it does that correctly (Validation). We hope that this helps communicate UOR to academic and technical audiences, and that it helps people be able to use UOR to regain our compute and data sovereignty.

[Same footer too about don't edit here]

[afflom]

Implemented in wiki commit 3a62f34.

• Landing page is live at https://github.com/UOR-Foundation/UOR-Framework/wiki/Scientific-Methods-and-Results with Robin's content under the # Scientific Methods and Results heading. Footer ("don't edit here") inherited from the wiki frame.
• Sidebar entry added under a new "Scientific Methods and Results" section.
• SOP documented in the wiki repo's README.md: Robin opens issues → wiki maintainer authors AsciiDoc under src/scientific/ → ./scripts/build.sh → commit + push.
• Partition specification added to wiki-definition.md under a new Non-normative content partitions section that records the academic-documentation stream as distinct from the three normative standards (arc42+C4, OPM ISO 19450, ISO 15288). All eight validators (V1–V8) pass; Stage 5 idempotence holds.

Future page additions: open an issue with the page slug + content; the maintainer adds src/scientific/<Slug>.adoc and the build pipeline takes care of staging.