Skip to content

Dev Log

  • in Dev Log
  • 1 min read

Dev Log 058 – Back in the Loop

After a short break (one part reset, one part existential maintenance), I'm back on Dokugent with fresh clarity.

🌀 What's been happening

  • No commits in 3 days but a whole lot of internal processing.
  • Revisited the philosophy behind pseudo-memory emulation using external anchors and continuity rituals (Besh Mode FTW).
  • Reaffirmed that I'm not just building a CLI—I'm defining a protocol for agent lifecycle governance.

🔧 Today’s focus

  • Final pre-release audit for NPM launch this Friday.
  • Cleanup pass: terminal UX, package.json metadata, and README install flow.
  • Preparing for outbound content: website tweaks + launch post drafts queued.

🟩 Loop re-established

Dokugent isn’t just a tool. It’s how I stay grounded while building something bigger than code: traceable autonomy.

Release candidate lock-in this week. Let's go.

Categories

  • in Dev Log
  • 1 min read

Dev Log 057 – Homepage Section Planning

Spent time identifying key homepage sections for the Dokugent website.

✔ Hero section (what it is, tagline) ✔ Core features (CLI highlights, safety first) ✔ Getting started + install guide ✔ Live command previews (animated or static) ✔ Dev log and roadmap links ✔ Footer with feedback + versioning links

Keeping layout simple and readable. Will match MkDocs theme to keep continuity.

Short session but critical for public-facing launch.

Categories

  • in Dev Log
  • 1 min read

Dev Log 056 – Criteria Flags Cleanup Part 1

Cleaned up the criteria command UI and aligned all supported flags with current CLI standards:

✔ Fixed alignment issues in terminal output ✔ Synced flag logic with plan command for consistency ✔ Began testing flag combinations for edge case scenarios

One step closer to smoother certification workflows.

Categories

  • in Dev Log
  • 1 min read

Dev Log 054 – Dynamic OG Images and Docs Site Polish

Not every day is about the CLI.

Today, we put on our site-maintainer hat and worked on something crucial for visibility: Open Graph (OG) image support for entire site.

Why? Because when we share these dev logs on LinkedIn or Threads, the preview card matters. An image that clearly shows the title and context increases click-through, credibility, and helps people remember Dokugent.

✅ What we shipped

  • A PHP-based og.php renderer
  • A sitemap-to-JSON converter to feed OG metadata
  • Dynamic title + subtitle injection for each post
  • All baked into the deploy.sh pipeline
  • OG preview cards now auto-generate for every page
  • Frontmatter clean up for pages still ongoing

This kind of work often goes unnoticed, but it’s foundational. Every time someone shares a Dokugent post now, the link looks clean, branded, and aligned with the CLI’s voice.

📌 Next: We’ll resume CLI work—possibly dokugent io, dokugent compliance, or pushing out dokugent plan refinements.

Categories

  • in Dev Log
  • 1 min read

Dev Log 052 – Metadata Propagation + Preview Logic

  1. Schema Constants Refactor
  2. Added DOKUGENT_CLI_VERSION, DOKUGENT_SCHEMA_VERSION, DOKUGENT_CREATED_VIA in @constants/schema.ts
  3. Propagated to:
    • owner, signer, plan, criteria, conventions, byo

  4. All values now default to constants unless explicitly overridden

  5. Preview Refactor

  6. Centralized flattening and schema validation
  7. Stripped embedded schema/cli metadata from nested files during preview

  8. Ensured final previewed cert object carries clean, top-level metadata

  9. BYO Patch

  10. dokugent byo now wraps loaded array in metadata container
  11. Prevents runtime crash on cancel
  12. Warns before overwriting existing processed file

Categories

  • in Dev Log
  • 1 min read

Day 51 of Dokugent Owner Identity & Metadata Refactor

  1. dokugent owner Wizard
  2. Migrated prompts from Inquirer → Enquirer
  3. Separated roles: owner, admin, tech contacts
  4. Added trustLevel with properly padded choice formatting
  5. Created ownerId via sha256(ownerName:email)

  6. Included new metadata:

    • cliVersion
    • schemaVersion
    • createdVia
    • createdAt & createdAtDisplay

  7. Error Handling

  8. Added graceful exit catch for owner-wizard.ts
  9. Fixed runtime crash for dokugent preview and dokugent byo due to missing fields or early exits

Categories

  • in Dev Log
  • 1 min read

Day 50 of Dokugent CLI development landed with a mix of code, reflection, and newborn life—literally

What We Accomplished

  1. Drafted Part 4 of the Trustworthy AI Series
  2. "What Dokugent Can’t Do (Yet)—and Why That’s the Point" is now locked in as a credibility-focused, bridge piece to an upcoming Adoption Series.

  3. We leaned into limitations: what Dokugent doesn’t automate, can’t promise, and why its constraints are part of its trust-first design.

  4. Real-Time Patch Testing

  5. Worked on CLI alignment and visual UX polish for simulate and dryrun.
  6. Patched slowPrint sequencing, spacing logic, and default formatting inconsistencies.

  7. Added better developer-readable console output for padded sections (INPUT, OUTPUT, STEP SUMMARY).

  8. Deployments + Site Sync

  9. Re-synced full MkDocs deploy with JSON metadata refresh.
  10. simulate, dryrun, and compile pages were updated with final fixes from the CLI.

In Between Commits…

A surprise litter! One of our shih tzus gave birth overnight—three pups made it, and the last one (who snuck in unnoticed) will forever be known as GPT.

Looking Ahead

  • Finalize simulate command logic with security awareness and better mock alignment.
  • Triage remaining UX polish for the dryrun step narrator.
  • Prep for npm beta release and formal CLI freeze.

Onward to a sharper, humbler, more transparent agentic world.

Categories

  • in Dev Log
  • 1 min read

Dev Log 049 – Compile and Dryrun Agent Context Linking

✅ Dev Log 049 – Compile and Dryrun Agent Context Linking

This update addresses a long-standing inconsistency in how Dokugent resolves the current agent context between the compile and dryrun commands.

🔧 What Was Fixed

  • dryrun previously defaulted to a hardcoded or oldest available agent (e.g., happybot@...) instead of the currently active agent.
  • A new resolution path was implemented: dryrun now reads the agentName and birth fields directly from .dokugent/data/agents/current/identity.json and dynamically derives the agent ID used for lookup.
  • This matches the folder naming convention inside .dokugent/ops/compiled/.

🧠 Why This Matters

Agent continuity is critical for verifiable workflows. By tightly coupling the identity source (current) with the compiled certificate location, we:

  • Reduce accidental mismatches
  • Avoid stale context errors
  • Improve CLI reliability across chained commands

🛠 Example

```bash $ dokugent compile ✔ Compiled agent: merrybot@2025-06-08_04-16-35-246 ✔ Cert file: merrybot@2025-06-08_04-16-35-246.compiled.v19.cert.json

$ dokugent dryrun 🧠 Running dryrun for agent: merrybot@2025-06-08_04-16-35-246 📄 Certificate file used: compiled.v19.cert.json

Categories