Writing at the source

Stories behind the work.

Creative work, accessibility and participation across the Loptr Lab ecosystem. Read each story in its original publication.

This first collection features the founder’s Made Sick publication. Articles reflect their publication dates; design notes are not proof that a feature has shipped.

9 stories

Jacque Fresco beside the Venus Project grounds, with its emblem and buildings among trees.

Mission · Founder publication

What would change if our systems made room for us?

Discovering The Venus Project through Ren, and connecting its ideas to accessibility, creator control, community and responsible uses of AI.

Read on pckt.blog ↗

Mission · Founder publication

People over profit. Accessibility first. Participation on clear terms.

The mission, voluntary participation terms and boundaries for supporting the Loptr Lab ecosystem.

Read on pckt.blog ↗

Storytelling · Founder publication

Have You Noticed?

How a public Bluesky feed became a story through recurring references and themes.

Read on pckt.blog ↗

Development · Founder publication

How I Architected Three Games in One Session Without Writing a Line of Code

A development account about game architecture, written contracts and decisions left open.

Read on pckt.blog ↗

Mission · Founder publication

One Gravity Well vs. A Universe With Depth

Why the ecosystem connects distinct projects while preserving their individual purposes.

Read on pckt.blog ↗

Development · Founder publication

PIXIE HAS ANOTHER DOOR.

An introduction to another door into the PIXIE ecosystem.

Read on pckt.blog ↗

Development · Founder publication

Architectural Note: Building an AT Proto-Native OS with Local-First Privacy

A published architectural design note about identity, local data and the proposed PIXIE workspace.

Read on pckt.blog ↗

Mission · Founder publication

LOG // 001 - The Cost of Unbounded Growth

A reflection on capacity, stewardship and the cost of unbounded growth.

Read on pckt.blog ↗

Accessibility · Founder publication

Your File System Is an Accessibility Tool — Apple Just Never Told You That

A creator’s perspective on file organization as an accessibility tool.

Read on pckt.blog ↗

Your work across the ATmosphere

Let your work speak.

A story or milestone write-up published through pckt.blog can live in your own AT Protocol repository. Sifa supports these Standard.site documents as creation activity. Your Made Sick participant record is separate: joining or adding a profile introduction does not publish an achievement.

  1. Publish your own story or milestone write-up through pckt.blog using the identity you want credited. Keep an existing article at its source rather than publishing a duplicate.
  2. Use the check below to inspect that identity’s public Standard.site documents.
  3. Open Sifa to check your profile. Sifa controls indexing and visibility; finding a record here does not confirm it appears there.

This lookup reads public record titles, dates and source links from the identity’s provider. It does not sign you in, publish, save an archive, or add work to the featured collection above. Repository control does not independently verify authorship or claims. Do not publish private health details to test this flow.

Nothing fetched until you choose Check published work.

How Sifa chooses activity · Sifa’s supported apps

Your story, your choice.

Directory participation and story featuring are separate choices. Other creators’ stories require permission for the specific title, excerpt, image, attribution and source link before a card is added. Joining Made Sick or exporting a Story Finder ledger does not grant that permission.

To propose a story or request a correction or card removal, contact Made Sick on Bluesky or use GitHub issues. Public posts and issues are public; share only the minimum information needed to identify the card. No diagnosis or private story is required. Removing a card leaves the original publication under its creator’s control; copies others made may remain.

Expressing interest does not publish a story. The participant join flow can publish a separate public participant record after its consent step.