New pages

19 June 2026

• 03:0803:08, 19 June 2026 Brief: EDURange is More Than a CRUD Architecture (hist | edit) [13,460 bytes] Jwgranville (talk | contribs) (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...") Tag: Visual edit: Switched

16 June 2026

• 04:0704:07, 16 June 2026 Message Bus Service (hist | edit) [320 bytes] Jwgranville (talk | contribs) (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") Tag: Visual edit
• 04:0604:06, 16 June 2026 Message Bus Live Coding Exercise (hist | edit) [61,747 bytes] Jwgranville (talk | contribs) (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...") Tag: Visual edit: Switched

6 June 2026

• 01:2901:29, 6 June 2026 TTY BPF Instrument Project Charter (hist | edit) [6,165 bytes] Jwgranville (talk | contribs) (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...") Tag: Visual edit

5 June 2026

• 23:5423:54, 5 June 2026 Message Bus Project Charter (hist | edit) [3,740 bytes] Jwgranville (talk | contribs) (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...") Tag: Visual edit

4 June 2026

• 16:1716:17, 4 June 2026 TTY BPF Instrument (hist | edit) [9,911 bytes] Jwgranville (talk | contribs) (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...") Tag: Visual edit

27 April 2026

• 18:5118:51, 27 April 2026 Data Store Project Charter (hist | edit) [3,535 bytes] Jwgranville (talk | contribs) (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...") Tag: Visual edit

31 March 2026

• 19:2319:23, 31 March 2026 Team Charter (hist | edit) [3,047 bytes] Jwgranville (talk | contribs) (Created page with "change me!") Tag: Visual edit