CorvidLabs / examples
← All examples

03 / An everyday app

Tiny Tasks

Add it. Finish it. Reopen it when plans change, with its earlier steps still there.

Try now ↓

Make it do something.

Open full screen ↗

Your first minute

  1. Add a short task, then mark it complete.
  2. Reopen it if plans change. Its history keeps the earlier steps.
  3. Export a JSON copy whenever you want a backup.

Small on purpose

Tasks live in this browser on this site. Clearing browser data removes them. Export is a backup; this example has no import.

The app needs JavaScript. There is no account or server connection.

Open it. Run it. Change it.

A whole little project.

Source, focused tests, build scripts and a README. MIT licensed. Nothing depends on a private repository.

Download source ZIP ↓Download Git history ↓

AFTER EXTRACTING THE SOURCE ZIP

cd tiny-tasks
bun install --frozen-lockfile
bun run test
bun run typecheck
bun run build
bun run start

Install Bun first. Setup downloads the pinned development compiler; the built app runs locally. Read the README for its local URL.

Verify the download hashes

Compare SHA-256 with shasum -a 256 filename.

Source ZIP
c5c8925fa509aad51c0c2d8d5f9c10a5686321607fc29b2bf9c041b936e31392
Git bundle
fbb668990e531634dafeb13e0b51a667e2316e1c2046c232a22bb0247d9e4b62

The build story

From an idea
to something you can use.

Saving can fail. The app should tell you and keep your current work on screen.

  1. 01

    PRODUCT · INTENT

    Say what should happen.

    A person approved five small examples that visitors can try, download and learn from. HI keeps the agreed intent in plain sentences.

  2. 02

    DESIGN · EXPERIENCE

    Make the idea visible.

    The gallery and five visual directions were reviewed before implementation. The approved design pairs a clear first action with a usable mobile layout.

  3. 03

    DEVELOPMENT · PLAN & BUILD

    Agree on the rules, then build.

    Task history stays in order. Invalid stored data is rejected. A failed save never discards current tasks.

    SpecSync records the contract. A Sol coding agent writes the implementation in an assigned directory. chough records the stage and handoff.

  4. 04

    QA · TEST & REPAIR

    Check what actually happens.

    Tests were written against explicit unimplemented functions first. That failure is a development starting point, not a regression in a working app. Fledge runs the real tests again after implementation.

    45 behavioral tests / 133 assertions passed. An independent agent freshly extracted this source ZIP, installed its pinned dependencies, and passed the documented tests, strict source typecheck and build. Browser interaction was checked separately by the coordinator.

    Browser interaction, accessibility and fresh source extraction are checked separately. A structural SpecSync pass alone cannot prove those behaviors.

  5. 05

    EVERYONE · ACCEPT & RELEASE

    Review the result together.

    The project owner approved the design, scope and finished implementation (site revision d1ad28a3). Merge, publication and deployment are separate decisions.

The actual trail

Read the commits.

This is a project-only export of real development history. Filtering removes unrelated workspace files and redacts author email addresses, so these public commit IDs differ from the originals. Commit times describe saved revisions, not hours of agent effort. The saved Git name is the workspace identity; it does not establish human authorship or review.

  1. 6bae5399f
    test(examples): add failing behavioral tests before app implementation
  2. 776e92da9
    feat(examples): implement five standalone browser games and apps
Open the Git history on your machine
git clone tiny-tasks.bundle tiny-tasks-history
cd tiny-tasks-history
git log --oneline
git show HEAD

The history retains the apps/tiny-tasks/ project path. The source ZIP starts directly at the project root. No private remote is needed.

A closer look.

Tiny Tasks running in the browser
Actual browser capture · Three actual tasks with one completed on independently extracted source build. Source and capture identity are recorded in the verification package.

Make your own small thing

What would you change?

Start with one sentence about what you want. Keep the change small enough to try, explain and check.

Meet the workflow ↗Try another example →