Development storytelling
Internal build · ForgeOS rebuild planned
Golved's Devlogs
Turn scattered development work into a devlog your community can actually follow.
An evidence-led devlog pipeline that gathers relevant work from team and community context, builds one canonical dossier, checks it for private material and prepares channel-ready drafts for human review.
Discuss a build for your studioTHE RECIPIENT
Built around a real operating constraint.
Originally developed while Aura Forge was building its first game, The Forge, so meaningful progress would not disappear across daily development conversations.
Release work, community discussion, bugs, priorities and shipped features lived in different places. Reconstructing a trustworthy story at publishing time meant either losing context or spending hours rebuilding it.
THE CONSTRAINTS
Useful only if it respects the messy parts.
- 01
Drafts had to come from real source activity rather than a canned project narrative.
- 02
Private names, financial details, internal tooling and task identifiers had to stay out of public copy.
- 03
Publication needed a human review boundary while the system matured.
THE SYSTEM
A complete path—not another loose collection of tools.
Read-only collection from relevant development conversation records inside a defined time window.
One evidence-led project-story dossier as the canonical source.
Redaction and duplicate/canned-output checks before the dossier is usable.
Channel-ready Discord, Patreon, Facebook, LinkedIn and X drafts plus a readable public archive.
WORKING EVIDENCE
The claim sits beside the thing that supports it.
- The working source architecture and output rules are documented in the internal Golved system.
- Dossiers, channel variants and redaction checks are saved as durable artifacts.
- Published development stories remain readable at the public Aura Forge devlog.
OBSERVED OUTCOMES
What is known. Nothing padded.
One canonical dossier can produce several channel-ready drafts without rewriting the story independently for each destination.
The public archive preserves readable progress while private source material remains behind a redaction boundary.
BOUNDARIES
Automation stops where trust needs a person.
Current V1 saves drafts to disk; John reviews and publishes them manually.
Standing themes and project buckets are organising aids, not evidence.
The ForgeOS version is a planned rebuild, not the current delivered product.
COST TREATMENTInternal R&D · no client priceThe existing system was developed for Aura Forge's own game-production workflow.
Valuable on its own.
Golved's Devlogs can stand alone as a development-story system for any studio that ships more work than it has time to explain.
More powerful when connected.
Rebuilt for ForgeOS, it can become the public storytelling layer fed by approved development, community and release evidence.
ADAPTABILITY
The mechanism transfers. The implementation stays specific.
Define which studio channels and records are legitimate evidence sources.
Tune redaction, voice and platform formats without changing the canonical story.
Keep publication manual or add approved platform handoffs later.
NEXT STEP