{"batchcomplete":"","continue":{"lecontinue":"20260331192351|1088","continue":"-||"},"query":{"logevents":[{"logid":1098,"ns":0,"title":"Brief: EDURange is More Than a CRUD Architecture","pageid":546,"logpage":546,"revid":946,"params":{},"type":"create","action":"create","user":"Jwgranville","timestamp":"2026-06-19T03:08:49Z","comment":"Created page with \"{{DISPLAYTITLE:EDURange is More Than a CRUD Architecture}}  = Brief: EDURange is More Than a CRUD Architecture =  == The Up-Front Cost We Are Choosing to Pay ==  The architecture I have been proposing for the next version of EDURange asks the team to pay some real up-front costs. A message-oriented service architecture, append-only observation, explicit domain modeling, and model-driven development are not free. They require shared vocabulary, new learning, more delibera...\""},{"logid":1097,"ns":0,"title":"Message Bus Service","pageid":545,"logpage":545,"revid":930,"params":{},"type":"create","action":"create","user":"Jwgranville","timestamp":"2026-06-16T04:07:59Z","comment":"Created page with \"Module repository and wiki documentation are pending. This is a placeholder topic page to index resources related to the development of the message bus service.  == Related ==  === Project Charter === [[Message Bus Project Charter]]  === Examples, Tutorials, Supporting Documents === [[Message Bus Live Coding Exercise]]\""},{"logid":1096,"ns":0,"title":"Message Bus Live Coding Exercise","pageid":544,"logpage":544,"revid":929,"params":{},"type":"create","action":"create","user":"Jwgranville","timestamp":"2026-06-16T04:06:29Z","comment":"Created page with \"= Introduction =  == Audience and scope ==  This exercise is intended for EDURange developers learning how to write event processors with the message bus.  The packaged <code>mbus</code> and <code>aostore</code> modules are treated as read-only for this exercise. All new code belongs under a demonstration directory such as:  <pre lang=\"text\"> workspace/     mbus/     aostore/     demos/         __init__.py         event_processors/             __init__.py </pre>  The exe...\""},{"logid":1095,"ns":0,"title":"TTY BPF Instrument Project Charter","pageid":543,"logpage":543,"revid":927,"params":{},"type":"create","action":"create","user":"Jwgranville","timestamp":"2026-06-06T01:29:09Z","comment":"Created page with \"== Scoping Outline: ==  === Challenges: ===  * '''What:''' ''\"Create ways to...\" / \"Redesign the...\"'' ** Host-level observation instrument that can capture terminal byte activity at the kernel boundary without proxying, replacing, or modifying individual TTY devices. ** Modular BPF-based instrumentation pattern that preserves raw observations, identity context, ordering evidence, fragmentation metadata, timing calibration, and visible loss/status information, while keep...\""},{"logid":1094,"ns":0,"title":"Message Bus Project Charter","pageid":542,"logpage":542,"revid":925,"params":{},"type":"create","action":"create","user":"Jwgranville","timestamp":"2026-06-05T23:54:48Z","comment":"Created page with \"== Scoping Outline: ==  === Challenges: ===  * '''What:''' ''\"Create ways to...\" / \"Redesign the...\"'' ** Design a local message bus that allows independently developed software components to communicate through typed broadcast topics without tightly coupling producers to consumers. ** Create a communication substrate whose traffic can be captured, replayed, and inspected, so that system behavior can be reconstructed after the fact. ** Support early-stage teams in which...\""},{"logid":1093,"ns":0,"title":"TTY BPF Instrument","pageid":541,"logpage":541,"revid":922,"params":{},"type":"create","action":"create","user":"Jwgranville","timestamp":"2026-06-04T16:17:09Z","comment":"Created page with \"Demonstrations and preliminary documentation can be found at https://github.com/edurange/demo-bpf-tty-logger and https://github.com/edurange/prototype-tty-bpf-instrument. Wiki documentation is pending. Preliminary draft files are available in the Discord <code>#fileshare</code> channel and will be linked here once Wiki configuration is adjusted to support attached non-image documents.  == Summary == The TTY instrument is a BPF-based kernel observation tool for capturing...\""},{"logid":1092,"ns":0,"title":"Scenario 0","pageid":0,"logpage":537,"params":{},"type":"delete","action":"delete","user":"Jwgranville","timestamp":"2026-06-04T15:51:27Z","comment":"Orphaned. Content was: \"This page is dedicated to holding information and notes about Scenario 0.\", and the only contributor was \"[[Special:Contributions/CLSimpson|CLSimpson]]\" ([[User talk:CLSimpson|talk]])"},{"logid":1091,"ns":0,"title":"Data Store Project Charter","pageid":540,"logpage":540,"revid":918,"params":{},"type":"create","action":"create","user":"Jwgranville","timestamp":"2026-04-27T18:51:34Z","comment":"Created page with \"== Scoping Outline: ==  === Challenges: ===  * '''What:''' ''\"Create ways to...\" / \"Redesign the...\"'' ** Design a data governance process that does not require general users (often junior developers) to actively comply with and knowingly implement team-wide policy. ** Create a cohesive way for internal API consumers to specify their access, organization and persistence policies for application/experiment data. * '''For Whom:''' ''\"For <user>... (considering <other stake...\""},{"logid":1090,"ns":2,"title":"User:Leo G","pageid":0,"logpage":0,"params":{"oldgroups":[],"newgroups":["sysop","interface-admin","bureaucrat"],"oldmetadata":[],"newmetadata":[{"group":"sysop","expiry":"infinity"},{"group":"interface-admin","expiry":"infinity"},{"group":"bureaucrat","expiry":"infinity"}]},"type":"rights","action":"rights","user":"Jack","timestamp":"2026-04-03T20:46:33Z","comment":""},{"logid":1089,"ns":2,"title":"User:Leo G","pageid":0,"logpage":0,"params":{"userid":520},"type":"newusers","action":"create","user":"Leo G","timestamp":"2026-03-31T19:28:04Z","comment":""}]}}