Sprawl Correction - Project Sprawl - Jervis

[innov8tor3]

Sprawl has taken place in a number of ways, hindering clear action and progress.

1. Issue duplication, incoherence and overlap
2. HTML duplication, incoherence and overlap
3. Incoherence between issue and HTML
4. Failure to organise Web pages via GitHub Pages

To correct this situation, roughly two weeks have been spent bringing issues up to date, merging then where possible, referencing them from each other using the issue hash capability, and linking in related Web pages.

This is not completely finished, and a modus operandi is needed moving forward.

We will likely create press, progress and use case pages on a blog style basis, quoting previous and next.

There's also the question of the Notion database saved from Bankless to consider. Rich pickings for historians.

[innov8tor3]

Following a decision to use Agentic AI, Project Sprawl has been tasked to Jervis, a coordination Agent also tasked with testing and harnessing AAI Agents.

The following tasks can be useful.

1. GitHub Pages utilities listing contents in clickable therefore displayable format
2. Linking GitHub Issues raised to current WIP, and the generated digital assets in the GitHub Pages repo

The following consideration will be helpful.

Is Project Sprawl simply an annoying itch that need not be scratched, or will solutions provide genuine function when navigating and assessing project-engine for next steps, prioritisation and overall status.

[innov8tor3]

Amalgamated into Issue #54 .