HAMANAKA / SOFTWARE FACTORY

IDEAS / TOOLS / REVIEWABLE RESULTS

Inside the
Software Factory.

One project at a time: what goes in, what the software does, and what comes out.

Generated illustrations and moving work packets explain project roles. The factory path is conceptual; each project retains its own maturity and limits.

  1. 01 Define
  2. 02 Build with AI
  3. 03 Check
  4. 04 Human review
  5. 05 Share / demo

Explore the workflow and revision loop ↗

ANIMATED PROJECT WALKTHROUGH

ai-dashboard

Integration hub

ai-dashboard illustrated input, operation and output

Understand the state of AI-assisted work from one local operator surface.

Inspect the published description ↗

Illustrations, not application screenshots or recorded executions. See actual software captures.

AI DASHBOARD / A CLOSER LOOK

One command center.
Four perspectives.

Work, inference, resources and evidence—brought into an operator’s view.

These richer concept scenes expand the categories already described in the public atlas. They are illustrations of a private project, not its actual interface or live data.

AI Dashboard concept: Work and agents

CHAPTER 01 / WORK AND AGENTS

Keep the task beside the activity.

Task tickets and agent work are shown together, giving the operator a place to inspect what is being worked on.

AI Dashboard concept: Inference activity

CHAPTER 02 / INFERENCE ACTIVITY

See requests moving through the work.

This concept follows inference requests and responses through an activity view, without presenting invented provider routes or live throughput.

AI Dashboard concept: Spend and machine health

CHAPTER 03 / SPEND AND MACHINE HEALTH

Bring costs and constraints into view.

Spending signals and machine-health categories sit beside the work, so the operator can inspect the resources involved.

AI Dashboard concept: Evidence and human inspection

CHAPTER 04 / EVIDENCE AND HUMAN INSPECTION

Make the result inspectable.

Results arrive with evidence for a person to examine. The scene illustrates review, not automatic acceptance or a production-readiness claim.

THE SELECTED WORKSHOP

39 projects.
Each with a purpose.

23 public projects and 16 private concepts, based on their already-public descriptions. Selection reviewed on 3 November 2026. Factory tools come first; independent product and creative experiments finish the tour. Each project has its own animated loop.

01 / NEXT PART OF THE WORKSHOP

Factory core

ai-dashboard: Agents, tickets and signals → Bring work into view → Local operator overview. Generated illustration.
01 / Factory core

ai-dashboard

Integration hub

Understand the state of AI-assisted work from one local operator surface.

  1. INPUTAgents, tickets and signals
  2. OPERATIONBring work into view
  3. OUTPUTLocal operator overview
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review operator information
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. The local command center where I bring agents, inference, tickets, spend, evidence and machine health together.

Read the published description ↗
Public description ↗Still image
cofoundry: Job and readiness signals → Supervise local work → Audited control record. Generated illustration.
02 / Factory core

cofoundry

Private engine

Explore local job supervision with readiness and control information kept visible.

  1. INPUTJob and readiness signals
  2. OPERATIONSupervise local work
  3. OUTPUTAudited control record
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review readiness and controls
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Packaged supervisor, job dispatch, local execution, readiness and audited controls.

Read the published description ↗
Public description ↗Still image

03 / NEXT PART OF THE WORKSHOP

Workflow and sessions

panther-intent-capture: Chosen browser activity → Capture and review intent → Improvement request. Generated illustration.
03 / Factory workflow

panther-intent-capture

Browser capture tool

Turn a confusing browser workflow into a request that retains the observed evidence.

  1. INPUTChosen browser activity
  2. OPERATIONCapture and review intent
  3. OUTPUTImprovement request
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Review capture and request
  4. Review Person decides the next step

Creates tickets, not implementations. Capture is opt-in; hypotheses are not verified defects; unsupported media/browser paths remain excluded.

Read the source at this revision ↗
Open repository ↗Still image
panther-companion: Selected evidence → Explain in goal context → Meaning and next check. Generated illustration.
04 / Factory workflow

panther-companion

Local workspace

Help a person interpret a result in relation to the task they are trying to finish.

  1. INPUTSelected evidence
  2. OPERATIONExplain in goal context
  3. OUTPUTMeaning and next check
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Trace explanation to evidence
  4. Review Person decides the next step

Inputs are selected or explicitly configured. Importing evidence does not authorize execution; optional sources and model use remain separate choices.

Read the source at this revision ↗
Open repository ↗Still image
muse-connector-tools: Conversation handoff → Coordinate host tools → Resumable local record. Generated illustration.
05 / Factory workflow

muse-connector-tools

Private workspace

Explore a host-assisted conversation handoff with a local record for resumption.

  1. INPUTConversation handoff
  2. OPERATIONCoordinate host tools
  3. OUTPUTResumable local record
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review a generic host handoff
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Host-assisted conversation tools with a resumable local ledger.

Read the published description ↗
Public description ↗Still image
el-hidratador: Approved task → Prepare bounded context → Staged work packet. Generated illustration.
06 / Factory workflow

el-hidratador

Documented local core

Give an AI task enough context and a clear scope without confusing eligibility with permission.

  1. INPUTApproved task
  2. OPERATIONPrepare bounded context
  3. OUTPUTStaged work packet
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check scope and ownership
  4. Review Person decides the next step

Core has no network or shell execution. It stages and records work; routing eligibility is not execution authorization and a person accepts the result.

Read the source at this revision ↗
Open repository ↗Still image
taskrivet: Task, context and agent → Work in persistent terminals → Reviewable session evidence. Generated illustration.
07 / Factory workflow

taskrivet

Desktop alpha

Keep the objective and evidence with an AI coding session instead of repeatedly rebuilding context.

  1. INPUTTask, context and agent
  2. OPERATIONWork in persistent terminals
  3. OUTPUTReviewable session evidence
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check session and evidence flow
  4. Review Person decides the next step

Mac app is unsigned and unnotarized; supervised selection and review remain explicit. Automated ticket selection, verified routing and autonomous acceptance are proposed.

Read the source at this revision ↗
Open repository ↗Still image
osprey: Selected terminal output → Redact and draft → Checkpoint proposal. Generated illustration.
08 / Factory workflow

osprey

Pre-release

Turn selected terminal activity into reviewable work records while keeping approval with a person.

  1. INPUTSelected terminal output
  2. OPERATIONRedact and draft
  3. OUTPUTCheckpoint proposal
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check redaction and approval
  4. Review Person decides the next step

Local Taskrivet supervisor; capture is read-only and ledger write requires explicit approval. It does not complete tasks or diagnose failures.

Read the source at this revision ↗
Open repository ↗Still image
fluxrecord: Task and evidence → Record work and review → Accepted work record. Generated illustration.
09 / Factory workflow

fluxrecord

Documented local core

Preserve objective, ownership, progress and failures when work crosses agent sessions.

  1. INPUTTask and evidence
  2. OPERATIONRecord work and review
  3. OUTPUTAccepted work record
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check review transition
  4. Review Person decides the next step

Worker finish creates review; only an operator decision creates done. No automated universal shipping claim is made by this illustration.

Read the source at this revision ↗
Open repository ↗Still image

10 / NEXT PART OF THE WORKSHOP

Verification and learning

el-verificador: Change and criteria → Inspect independently → Verdict and audit record. Generated illustration.
10 / Review and verification

el-verificador

Alpha; pipeline separate

Check a change against intent and acceptance criteria before treating the work as complete.

  1. INPUTChange and criteria
  2. OPERATIONInspect independently
  3. OUTPUTVerdict and audit record
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Compare evidence to criteria
  4. Review Person decides the next step

Core verification loop is documented as implemented; the wider pipeline is explicitly not connected. Audit ledger is local, not a canonical external receipt.

Read the source at this revision ↗
Open repository ↗Still image
counterfactory: Workflow rules → Explore failure orders → Counterexample trace. Generated illustration.
11 / Review and verification

counterfactory

Research preview

Understand how a lost reply can cause duplicate work even when individual components look healthy.

  1. INPUTWorkflow rules
  2. OPERATIONExplore failure orders
  3. OUTPUTCounterexample trace
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Replay failure traces
  4. Review Person decides the next step

Synthetic finite models; a passing model does not prove a production implementation matches its assumptions.

Read the source at this revision ↗
Open repository ↗Still image
agent-recovery-bench: Recovery scenarios → Rehearse interruptions → Recovery observations. Generated illustration.
12 / Review and verification

agent-recovery-bench

Private benchmark

Explore how coding workflows resume after interruptions using offline scenarios.

  1. INPUTRecovery scenarios
  2. OPERATIONRehearse interruptions
  3. OUTPUTRecovery observations
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Inspect a recovery scenario
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Offline recovery scenarios for coding workflows; a benchmark workspace, not customer delivery evidence.

Read the published description ↗
Public description ↗Still image
reality-boundary-standard: Claim and evidence → Declare scope and limits → Reviewable claim record. Generated illustration.
13 / Review and verification

reality-boundary-standard

Proposed standard

State what a technical claim actually supports and what remains a proposal.

  1. INPUTClaim and evidence
  2. OPERATIONDeclare scope and limits
  3. OUTPUTReviewable claim record
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check claim scope and evidence
  4. Review Person decides the next step

0.1.0 draft with no certification program. Structural validation does not establish factual truth or full conformance.

Read the source at this revision ↗
Open repository ↗Still image
the-chronicler: Failure history → Extract reusable lessons → Rules and documentation. Generated illustration.
14 / Factory workflow

the-chronicler

Documented local daemon

Avoid repeating the same setup mistakes by retaining lessons from prior failures.

  1. INPUTFailure history
  2. OPERATIONExtract reusable lessons
  3. OUTPUTRules and documentation
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Review proposed lessons
  4. Review Person decides the next step

README describes configured local ledger and model inputs plus repository writes. This review did not establish a live end-to-end factory integration or validate model conclusions.

Read the source at this revision ↗
Open repository ↗Still image

15 / NEXT PART OF THE WORKSHOP

Testing fixtures

mockmill: Scenario and seed → Generate linked records → Offline CRM fixtures. Generated illustration.
15 / Synthetic data

mockmill

Synthetic; offline

Test workflows with coherent fictional business data instead of disconnected sample rows or real customer records.

  1. INPUTScenario and seed
  2. OPERATIONGenerate linked records
  3. OUTPUTOffline CRM fixtures
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Validate links and arithmetic
  4. Review Person decides the next step

Every person, company and transaction is fictional. Adapters generate CSV/JSON fixtures and do not perform live CRM imports.

Read the source at this revision ↗
Open repository ↗Still image
storyfoundry-public-fixture: Fictional scenario → Generate and validate → Training records. Generated illustration.
16 / Synthetic data

storyfoundry-public-fixture

Synthetic; offline

Practice CRM workflows on a deterministic fictional service-company history.

  1. INPUTFictional scenario
  2. OPERATIONGenerate and validate
  3. OUTPUTTraining records
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Replay and validate the fixture
  4. Review Person decides the next step

All company, person and transaction records are fictional. Import preview is a dry run with no target client and no authority to contact or charge anyone.

Read the source at this revision ↗
Open repository ↗Still image
vs-platform-synthetic-fleet: Synthetic nodes and messages → Exercise protocol fixtures → Test scenario observations. Generated illustration.
17 / Synthetic data

vs-platform-synthetic-fleet

Private simulation

Explore platform behavior with fictional hardware nodes and protocol fixtures.

  1. INPUTSynthetic nodes and messages
  2. OPERATIONExercise protocol fixtures
  3. OUTPUTTest scenario observations
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review a protocol fixture
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Synthetic hardware nodes and protocol fixtures for platform testing.

Read the published description ↗
Public description ↗Still image

18 / NEXT PART OF THE WORKSHOP

Local compute and transport

the-surveyor: Local system observations → Map and compare → Topology change record. Generated illustration.
18 / Compute and transport

the-surveyor

Read-only survey tool

Understand what is actually present on a machine and what changed since the previous survey.

  1. INPUTLocal system observations
  2. OPERATIONMap and compare
  3. OUTPUTTopology change record
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Compare observations and changes
  4. Review Person decides the next step

Observes the box on which it runs; a topology map is not proof that remote services or integrations work. Notifications require configuration.

Read the source at this revision ↗
Open repository ↗Still image
the-tower: Telemetry and task request → Assess capacity → Clearance recommendation. Generated illustration.
19 / Compute and transport

the-tower

Advisory prototype

Make local compute decisions visible against resource conditions and explicit controls.

  1. INPUTTelemetry and task request
  2. OPERATIONAssess capacity
  3. OUTPUTClearance recommendation
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check advisory and enforce boundary
  4. Review Person decides the next step

Two of three demo nodes are simulated; macOS temperature is estimated. Fresh installs are advisory; enforcement requires explicit per-node opt-in.

Read the source at this revision ↗
Open repository ↗Still image
horizon-broker: Inference jobs → Queue and route → Results or recovery state. Generated illustration.
20 / Compute and transport

horizon-broker

Alpha

Keep local inference work inspectable when jobs take time or a worker stops responding.

  1. INPUTInference jobs
  2. OPERATIONQueue and route
  3. OUTPUTResults or recovery state
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check failed-worker recovery
  4. Review Person decides the next step

One broker owns one fleet; external ledger adapter is not complete. KV handoff depends on engine support; Ollama degrades to whole-job execution.

Read the source at this revision ↗
Open repository ↗Still image
bumperfort: Vectors and state → Calculate motion → Trajectory results. Generated illustration.
21 / Compute experiments

bumperfort

Educational core

Explore deterministic numerical kernels and the interface between numerical code and other tools.

  1. INPUTVectors and state
  2. OPERATIONCalculate motion
  3. OUTPUTTrajectory results
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check numerical cases
  4. Review Person decides the next step

README calls v0.1.0 an educational and usable core. Wider agent-embedding and hardware metaphors are a vision, not a qualified production claim.

Read the source at this revision ↗
Open repository ↗Still image
lineasflow: Shared-memory state → Broadcast binary updates → Local mesh state. Generated illustration.
22 / Compute and transport

lineasflow

Documented daemon

Move numerical state from a local producer to other machines without a JSON conversion step.

  1. INPUTShared-memory state
  2. OPERATIONBroadcast binary updates
  3. OUTPUTLocal mesh state
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check binary round trips
  4. Review Person decides the next step

README describes shared-memory and UDP multicast components. No live multi-node deployment or benchmark result was verified for this visual.

Read the source at this revision ↗
Open repository ↗Still image
VortexMesh: Validated event → Route, retain, reconcile → Inspectable event state. Generated illustration.
23 / Compute and transport

VortexMesh

Learning components

Explore small transport components for events crossing intermittent links.

  1. INPUTValidated event
  2. OPERATIONRoute, retain, reconcile
  3. OUTPUTInspectable event state
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check component boundaries
  4. Review Person decides the next step

Transport, WAL and reconciliation are separately implemented; no daemon connects them end to end. Authorization, discovery adapters and other deployment pieces remain planned.

Read the source at this revision ↗
Open repository ↗Still image

24 / NEXT PART OF THE WORKSHOP

EdgeRecord — separate venture

edgerecord: Local evidence → Organize and verify → Reviewable evidence. Generated illustration.
24 / Evidence and records

edgerecord

Private workspace

Keep local verification material organized for review.

  1. INPUTLocal evidence
  2. OPERATIONOrganize and verify
  3. OUTPUTReviewable evidence
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review evidence provenance
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Local verification and evidence workspace.

Read the published description ↗
Public description ↗Still image
edgerecord-core: Edge-node state records → Verify append-only state → Verification result. Generated illustration.
25 / Evidence and records

edgerecord-core

Private verifier

Explore deterministic checks of append-only state records from edge nodes.

  1. INPUTEdge-node state records
  2. OPERATIONVerify append-only state
  3. OUTPUTVerification result
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review a synthetic state case
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Deterministic append-only state verification for edge nodes.

Read the published description ↗
Public description ↗Still image
edgerecord-era: Autonomy evidence → Retain ordered records → Evidence ledger. Generated illustration.
26 / Evidence and records

edgerecord-era

Private ledger

Keep autonomy-related evidence in an organized records ledger.

  1. INPUTAutonomy evidence
  2. OPERATIONRetain ordered records
  3. OUTPUTEvidence ledger
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review a sample receipt
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Autonomy evidence and records ledger.

Read the published description ↗
Public description ↗Still image
edgerecord-ai: Agent handoff context → Prepare a local handoff → Durable handoff record. Generated illustration.
27 / Factory core

edgerecord-ai

Private workspace

Explore carrying agent context through a durable local handoff.

  1. INPUTAgent handoff context
  2. OPERATIONPrepare a local handoff
  3. OUTPUTDurable handoff record
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review the handoff contract
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Local AI stack workspace and durable agent handoffs.

Read the published description ↗
Public description ↗Still image
edgerecord-com: Evidence workspace → Present tenant workspaces → Web shell concept. Generated illustration.
28 / Portfolio and communication

edgerecord-com

Private web shell

Explore a web surface for working with evidence across distinct tenant workspaces.

  1. INPUTEvidence workspace
  2. OPERATIONPresent tenant workspaces
  3. OUTPUTWeb shell concept
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review workspace separation
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. A multi-tenant web shell for the evidence workspace.

Read the published description ↗
Public description ↗Still image
edgerecord-publisher: Reviewed ledger receipt → Prepare publication → Article preview concept. Generated illustration.
29 / Portfolio and communication

edgerecord-publisher

Private publishing adapter

Explore how a reviewed receipt could become publishable material through Joomla Web Services.

  1. INPUTReviewed ledger receipt
  2. OPERATIONPrepare publication
  3. OUTPUTArticle preview concept
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review receipt-to-article text
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Publish reviewed ledger receipts through Joomla Web Services.

Read the published description ↗
Public description ↗Still image

30 / NEXT PART OF THE WORKSHOP

Publishing and orientation

hamanakam1: Selected project evidence → Present useful work → Contact path. Generated illustration.
30 / Portfolio and communication

hamanakam1

Public profile

Help a prospective customer understand relevant work and how to discuss a paid project.

  1. INPUTSelected project evidence
  2. OPERATIONPresent useful work
  3. OUTPUTContact path
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check links and readability
  4. Review Person decides the next step

This repository is the profile presentation, not a runtime factory component. Inventory text may lag the refreshed census.

Read the source at this revision ↗
Open repository ↗Still image
hamanakam1.github.io: Project stories → Organize and explain → Searchable portfolio. Generated illustration.
31 / Portfolio and communication

hamanakam1.github.io

Public website

Let a prospective customer explore software examples, scope and contact options.

  1. INPUTProject stories
  2. OPERATIONOrganize and explain
  3. OUTPUTSearchable portfolio
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check navigation and access
  4. Review Person decides the next step

Portfolio diagrams describe responsibilities and proposed handoffs; animation is illustrative, not live execution telemetry.

Read the source at this revision ↗
Open repository ↗Still image

32 / NEXT PART OF THE WORKSHOP

Product and creative experiments

meter-mouse-garden: Usage events → Store local readings → Usage view prototype. Generated illustration.
32 / Product experiments

meter-mouse-garden

Fixture-backed prototype

Make AI usage and agent-health information easier to inspect while separating observed values from estimates.

  1. INPUTUsage events
  2. OPERATIONStore local readings
  3. OUTPUTUsage view prototype
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Distinguish fixtures from live data
  4. Review Person decides the next step

Static dashboard currently uses fixture data; Rust daemon and SQLite ledger exist, but the frontend connection is the next increment.

Read the source at this revision ↗
Open repository ↗Still image
blessed-edge-deployment: Fictional hardware scenario → Rehearse local handoff → Reproducible demo bundle. Generated illustration.
33 / Product experiments

blessed-edge-deployment

Private local demo

Explain a hardware-to-handoff flow with local permissions and repeatable demonstration material.

  1. INPUTFictional hardware scenario
  2. OPERATIONRehearse local handoff
  3. OUTPUTReproducible demo bundle
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review demo permissions
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. A fictional hardware-to-handoff rehearsal with local permissions and reproducible bundles.

Read the published description ↗
Public description ↗Still image
onramp-synthetic-company: Fictional company records → Rehearse business workflows → Scenario observations. Generated illustration.
34 / Synthetic data

onramp-synthetic-company

Private simulation

Practice a business workflow using a fictional company dataset.

  1. INPUTFictional company records
  2. OPERATIONRehearse business workflows
  3. OUTPUTScenario observations
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review fictional scenario data
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. A fictional company dataset for local business-workflow rehearsals.

Read the published description ↗
Public description ↗Still image
cloudteams-extension-studio: Extension idea → Explore a local SDK → Extension concept. Generated illustration.
35 / Product experiments

cloudteams-extension-studio

Private prototype

Explore a small extension concept and the boundaries of a proposed browser-local SDK.

  1. INPUTExtension idea
  2. OPERATIONExplore a local SDK
  3. OUTPUTExtension concept
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review a proposed extension
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. Standalone extension concepts and a proposed browser-local SDK.

Read the published description ↗
Public description ↗Still image
cloudteams-lunch-break: Fictional planning scenario → Explore a gesture plan → Plan for human review. Generated illustration.
36 / Product experiments

cloudteams-lunch-break

Private experiment

Rehearse a fictional client-and-talent planning gesture with a visible human decision.

  1. INPUTFictional planning scenario
  2. OPERATIONExplore a gesture plan
  3. OUTPUTPlan for human review
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review fictional planning
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. A fictional client/talent gesture-planning demo derived from Extension Studio.

Read the published description ↗
Public description ↗Still image
cloudteams-plot-twist: Changed project conditions → Rehearse a response → Next-step proposal. Generated illustration.
37 / Product experiments

cloudteams-plot-twist

Private experiment

Explore how a project plan could respond when its circumstances change.

  1. INPUTChanged project conditions
  2. OPERATIONRehearse a response
  3. OUTPUTNext-step proposal
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Read the published project brief
  2. Build Explore a bounded concept
  3. Check Review a proposed response
  4. Review Person reviews the proposal

Concept from public description; private source not reviewed. A fictional demo for rehearsing changed project circumstances.

Read the published description ↗
Public description ↗Still image
murmuration: Feed, stir and seed → Simulate local behavior → Living browser pond. Generated illustration.
38 / Creative software

murmuration

Browser simulation

Create a playful interactive browser demonstration with inspectable simulation behavior and saved state.

  1. INPUTFeed, stir and seed
  2. OPERATIONSimulate local behavior
  3. OUTPUTLiving browser pond
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Check simulation and saved state
  4. Review Person decides the next step

Simplified artificial-life toy, not biological modeling or trained intelligence. JavaScript, Canvas 2D and WebGL are current; Odin/WASM is proposed.

Read the source at this revision ↗
Open repository ↗Still image
scratch-kitchen: Kitchen inventory → Plan, cook and transform → Meal and approved share. Generated illustration.
39 / Product experiments

scratch-kitchen

MVP scaffold

Use ingredients already on hand and turn surplus into a different meal or a deliberate share.

  1. INPUTKitchen inventory
  2. OPERATIONPlan, cook and transform
  3. OUTPUTMeal and approved share
Factory checkpoints & source

Proposed checkpoints for discussing this project:

  1. Frame Define the useful result
  2. Build Explore a bounded change
  3. Check Validate a proposed meal flow
  4. Review Person decides the next step

Illustrated product concept. Elixir/SwiftUI structure is not yet a compiled shippable application; proposed recognition and sharing behavior must be labeled.

Read the source at this revision ↗
Open repository ↗Still image

START WITH A REAL PROBLEM

What needs to work
better in your day?

I build prototypes and workflow tools with AI. Bring one recurring task or an idea you want to test, and we can discuss a small paid project with a result we can review together.

Discuss a project with Mike ↗