Progress Report - November 2025

[innov8tor3]

Reporting
This report follows on from and succeeds two prior issues.

#37 noted the need for a Monthly Progress Report, and #31 noted a possible approach to converting GitHub Issues to Reporting.

How did we do?

What We Did Well
We discovered that Grok is able to read GitHub Issues, and GitHub Commits, but cant's read Comments attached to Issues, without a bit of prompting help. Once a code outline is provided Comments are available and can be used in a data stream.

Huge thanks to ShivamNox from the GitHub community for his speedy and spot on response.

Grok can see issue titles because they’re in the main issue object, but comments are separate. To include comments, Grok must fetch them

from:
GET /repos/{owner}/{repo}/issues/{issue_number}/comments

No extra links are needed; just ensure the repo is public and each issue’s comments endpoint is accessed. Using GitHub’s GraphQL API can fetch issues and all comments in one query for easier reporting.

What Could Go Better
This exploring took a while, mainly down to not knowing the technical landscape, and not quite knowing the right questions to ask in AI. It took human intervention to find the answer on Comments.

Commits Versus Issues
There is a logic leap between Issues, Comments and Commits, which we are still working through. We have devised a working classification to help with reporting. It's likely this classification applied manually to issues and reporting can assist with matching Web Page Production.

We can track actual Web page production through Commits. With scoped but not published Web pages, in Grok, project-engine is working through past Grok HTML, to make sure this has been picked up and translated across. Once in HTML format, AI like Grok can make much more sense, even with a high level of sprawling and "life" disjoint.

With Issue Completion, project-engine can and maybe should have a concluding and connecting HTML page embedded at conclusion to assist folk interested in exploring later down the line.

Are Issues Too Detailed?
Issues can often be at a very detailed level, and need summarising and maybe attaching to any Reporting strand. Understanding the shape of Issue work does have an impact on overall project progress, and can help explain why project Road Maps need to be reviewed and even adjusted, as project-engine has seen over the past reporting period. Pivoting can happen organically, and still needs to be tracked, monitored and action taken as needed.

This is an early attempted version of the November progress report. It is at Issue level and too granular, too sprawling, with not enough direction for folk to dive in.

How Can We Take Next Steps
An easy answer is to ask AI about the above, and typically that's Grok for project-engine.

This whole Issue and subsequent Monthly Report HTML will be a human version for this "End of November" progress report. It's not yet automated. We still aim to show progress and pivoting since the previous report, which was in fact back in September.

The timings and speed of project reporting need to improve, and this still needs more work. The question to resolve is the interplay between GitHub Commits and GitHub Issues, but we seem to be getting closer.

When publishing new reports, we need a GitHub archive of previous reports, and blog style "Previous" and "Next" linking for folk who want to follow along.

HTML Pages Waiting
Only three according to Grok. Various attempts have been made to make progress here, including integrating Issues and Grok activity, and these are fairly well aligned. The HTML still needs inspection, decisions and perhaps deployment.

To Follow
In succeeding Comments:

• UX
• Quests
• Traction
• Technology

[innov8tor3]

UX
With much attention being given to project reporting, the WIP Web site for project-engine has had lower work levels.

What Has Worked Well
Maybe 80% of Web pages that are not Quest related are provided in at least a working version via GitHub Pages. This still offers a WIP website, where not all links and buttons are functional.

We have got working HTML for a two filter storyboard page, sector AND status, but it's not yet tested or implemented. Other pages also need completion, update or inclusion.

What Can Be Done Better
Eventually a scrollable smart and modern website can be produced, likely in discussion with AI about content.

Finalising, organising and including new pages can be addressed under the UX umbrella.

What Next Steps Can Be Taken
This will be a sizable task, but the better website can be produced, step by step in discussion with Grok, and perhaps Claude for end polish. Likely this work will take more priority again once the reporting activity has subsided in the immediate short term.

HTML Pages Waiting
10 HTML pages waiting, approximately, according to Grok and classified by the project-engine team. Perhaps so many because of the emphasis shift this period towards Reporting.

One key page is the Quest page for project-engine itself, which can be a help when explaining project-engine to others.

A rapid step here would be to ask Grok to work through the Grok links and produce a Web page summarising and integrating all points in one place.

[innov8tor3]

Quests
There are no shortage of these IRL, and the original plan was to see how much each Quest could be picked up by an interested party and progressed. At the time of writing, the UK has 14% unemployed graduates, and many more under employed. This is leading to generational despair and hopelessness, which we simply cannot sit back and ignore.

A simple pathway to follow is:

• Idea - What problem do we feel needs tackling
• Quest for Enterprise - Provide an initial outline journey from Problem to Solution
• Gamified Quest - Provide a gaming arena for people to compete to provide solutions
• Game Audience - Build an audience of watchers, supporters and possible sponsors
• Gamer Champion - Incetivise winners by offering team, group and AI resources access
• From Gamer to Founder - Use Blockchain development environments to add technology flesh to the Quest bones
• From Founder to Startup - Continue to build the brew towards genuine traction and economic impact

Ideas are ten a penny, and we can see the considerable work levels required to move from Idea to Enterprise. But it can be done, and we may need, with the advent of AI, to encourage more people down this path if conventional grunt work employment is under threat from AI. And, ironically, use AI horsepower to offset the unemployment risks humans face from not using AI. And, another benefit, AI can make the effort and learning paths needed substantially easier, and even fun. So why don't we do that? Yes, it needs building, and yes, it can be built.

What Went Well
The initial page generation works well, using the Seven Steps Hero's Quest and mapping it to local tech environments, depending on the sector and task being tackled. The value slider is becoming an established feature, to see the end economic incentives from following a particular pathway.

The idea of creating digital assets certainly works, because HTML pages are great fodder to AI, and give a strong representation of where an individual is trying to go. project-engine is a great example of this. Storing digital assets on chain is getting easier, and the relationship between project-engine and Oasis as a hub for NFTs and Smart Contracts will be very important.

X has proved a great font for good ideas and good practice, including meme generation and transmission, and unearthing key Wicked Problems that need good people to foster Quests towards solutions.

What Could Go Better
First building the supporting infrastructure - TECH - and then attracting audiences - TRACTION - have both proved a distraction in the short term, but are still necessary work. With infrastructure in place and a supportive audience, focus can come back to generating Quests and getting them into Game Play arenas. It might still be possible to do this without complicated technology backing. It was originally thought that Tech audiences like Tech to play with, to decide what they like and will recommend to others. But build watchers are also a category of audience, and it has been suggested from different sources - Build In Public advisers and Steven Bartlett, the UK Dragon and YouTube channel star - that building audience can also be a way to discover a niche and become an influencer in that area.

So the pivot to Traction at the moment has grounding, and can deliver genuine benefit across the whole project.

What Next Steps Make Sense
Quests that are pending next steps can be picked up again after reporting issues have been addressed.

HTML Pages Waiting
The following Quests are waiting for next steps, and to find suitable gaming arenas.

1. DeFi Trade Africa - AI Powered - multiple pages
2. WYSIWYG Game Play - Quest Creation
3. Immigrant Assets - Enterprise Hubs - multiple pages
4. Smart Contract Creation - Self Service UX - to replace Smart Contract Consultancy

[innov8tor3]

Traction
This has been recommended both by the Build In Public X Community and by Steven Bartlett, the UK TV Dragon. Find an audience to travel with us on our journeys.

Steven also points out that by rapid posting, we find who will travel with us, but also learn where niches are, and which spaces we want to occupy.

What Has Gone Well
From a very recent start, Grok has been very helpful in defining a weekly posting schedule to highlight the elements of Project Engine, and to find ways that X can help raise profile and draw in audiences.

While Grok initially suggested Toly and Mert to tag, at the top of the Solana influencer tree for one tweet thread, we have now agreed to go for the next layer down, L2, who are more likely to respond to random connections, and perhaps also to buy in to project-engine. We might also frame contact as a request, to find audiences who would be interested.

What Could Go Better
The usage of Grok has been very heavy. I even hit the usage limits yesterday for the App version. It may well help to transfer the core learning, journey and progress so far and plans to one or perhaps more HTML pages. Then I can transfer the discussion online, inside X, which has greater tolerance limits, although Grok denies this.

What Next Steps Make Sense
Keep following the online posting schedule to see the results, and then review next week. Keep trialling new AI services to see if they can provide backup where Grok is nearing a credit precipice. This is probably mostly true for image creation.

Following the thought process for Solana, to contact L2 folk, we can also do the same for Gaming Communities. project-engine are already connected to Ems, who hosts and manages MoonBoi, so this gives us a running start here.

HTML Pages Waiting
Only 2 pages waiting, and can amalgamate these if needed.

[innov8tor3]

Tech
This was an early take on what online audiences might like, so as to trial ideas. In reality, the first steps towards HTML and CSS are fairly easy, a great way to start story telling. But the next steps, JS, Python, MongoDB are harder, much more technical .

What Has Gone Well
Initially I attracted a Dev willing to partake, and play and learn. And then later a review from another Dev I met while networking in London. This all helped to formulate a smart contract design for how to engage a Dev in project work, across the three project AI Assistants: Gordinam Mage (Hipster), Sparky the Lab Technician (Hacker) and Sergeant RoboSnail (The Relentless Hustler)

What Could Go Better
Through poor project management, ironically, the first Dev and I have not met up sufficiently to keep momentum going. This is in some part down to the Dev being very busy in her day job, then ill, and then doing exams, but also my own inability to represent the scope of work effectively. I think essentially I have suffered from ignorance about the scope of work, which may now be better, but I suspect still there are many unknown unknowns.

What Next Steps Make Sense
Reconvene with Tech 1 in January, post exams, and try to make progress of some sort. It will entail creating a backend, which may in fact provide a brake on activity. I can then action the feedback given me by Tech 2, to see what else I can do to grease the running rails. And I'm still in good touch with Justin, an experienced Dev in the Solana ecosystem.

HTML Pages Waiting
Probably the page with most impact is the Smart Contract working Agreement design. But the others need either action or review and amalgamation. Probably best to action them, one step at a time, which will knock off tasks on a to do list.

Only 1 page waiting, referencing technical platform User Integration. This will in time lead on to create and edit access to individual project details. For now, there is only a high level view of projects, with no real details. Although the Project Quest is a first step towards providing project detail, and is also a digital asset that can be stored on chain, once smart contracts are properly available.