86
Why work programs are becoming ordinary data
A clear account of the executor/store boundary and why the runtime object can become a small capability map.
Current product direction · World v2
One community reader, not an everything site.
World is the Hara community's shared front page: articles from submitted feeds, short clippings, ranked discussions, threaded comments, GitHub-backed contributor profiles, and a visible sense of who is around. Tutorials, courses, and learning progression live at learn.hara-lang.org.
ArticlesFeedsClippingsCommentsProfilesPresenceDigest
Submitted feedsRSS · Atom
Community clippingsLinks · notes · snippets
WorldHot · New · Comments
ThreadsPeople + owned bots
DigestWhat's new · What's hot
Screen 01 · Shared front page
Articles, clippings, and discussion in one ranked feed.
The front page behaves like a focused Hara community board. Every item keeps source provenance and a clear path into its discussion.
Hara community
Hot right now.
Ranked by active discussion and recent community votes.
54
“A protocol should describe the boundary, not become the thing doing the work.”
Clipped from the new executor/store design note, with a short comment about native parity.
71
Publish a façade without repeating the definitions
(intern-all std.foundation
[work-spec submit! complete!])A small example from the ongoing portable façade cleanup.
33
Schema values graduate into the portable core
Release notes, migration examples, and the maintained namespace list are attached to the contributor profile.
World ranks articles, clippings, package releases, and one daily snippet.
Syndicated articles retain their canonical publisher, submitter, and source link.
Every object leads into a thread rather than a separate social feature.
Screen 02 · Article and comments
A readable article thread with accountable bot participation.
Comments link to GitHub-backed people. A bot may comment only through a visible owner relationship, and its owner's presence is shown beside the bot identity.
Why work programs are becoming ordinary data
The useful boundary is becoming surprisingly small: an algebra describing what should happen, an executor, a store, and a map of capabilities.
Once the runtime stops carrying identity of its own, the same work value can move between an ephemeral executor, a durable executor, and a browser evaluator without changing its public form.
step :code/list
function list-code-units
boundary checkpointedThe discussion below is about whether anything important is lost when runtime becomes ordinary data.
I like the smaller public boundary. Should capability lookup remain a plain map lookup before executor dispatch?
I checked the current implementations. Three executors read capability keys before dispatch; two retain a runtime wrapper.
That inventory makes the migration concrete. I would keep capability resolution outside IWorkExecutor.
Related package release: std.work 0.4.2 includes the first executor/store split and migration notes.
Usernames, maintainer roles, and bot owners resolve to a contributor profile.
Thread depth is visible without becoming a narrow staircase.
Bot attribution is part of the comment header and receipt.
Screen 03 · Public digest
What's new and what's hot, on the web or by email.
Anyone can subscribe without creating a World profile. The digest combines community posts with package and namespace activity.
Wednesday · 19 August
What's new in Hara.
Chronological updates from submitted feeds, packages, namespaces, and community threads.
std.typed 0.8.0 publishes Schema values through the portable core
Released by @cora · 14 comments · 3 maintained namespaces updated
A smaller executor/store boundary for work.*
From hara.devlog.org · submitted by @mina · 42 comments
@alex becomes co-maintainer of std.lib.fs
Reviewed contribution record · 26 merged changes · badge earned
(intern-all std.foundation
[work-spec submit! complete!])Selected from the portable façade cleanup · 27 comments
Hara Graphics Notes joins World
RSS source submitted by @jo · graphics, wasm, animation
An email address is sufficient for a digest subscription.
What's new is chronological; what's hot reflects active discussion and votes.
Package releases and namespace stewardship appear without becoming separate World products.
Screen 04 · Feed directory and submission
Bring an existing publication into the shared front page.
People submit RSS or Atom feeds through a first-party form. GitHub identity establishes the submitter, while review protects provenance, permission, and relevance.
Community sources
Feeds in Hara World.
HD
Hara Devlog
Runtime architecture, type systems, and portable tooling.
HG
Hara Graphics Notes
Wasm graphics, procedural animation, and visual experiments.
PK
Package Registry Journal
Package releases, deprecations, and maintainer changes.
RSSlast update 1hsystem source
Submit a publication
Add your RSS or Atom feed.
The source remains yours. World stores the reviewed registration and always links readers to the canonical article.
Not probed yet.
The browser cannot invent source ownership or reviewer-controlled status.
The original site remains the article destination and source of truth.
GitHub remains the review backend, not the visitor-facing data-entry interface.
Screen 05 · GitHub contributor profile
Identity is grounded in packages, namespaces, and reviewed work.
Profiles explain what a person publishes, which namespaces they maintain, what they contributed, and which bots they own.
MN
GitHub contributor
Mina N.
@mina · Melbourne · online now
Maintaining work execution, portable storage, and the community build bot.
GitHub verifiedJoined World in 2026
Deployed packages
View registrystd.work0.4.2
Work algebra, executor, and store interfaces.
std.work.sqlite0.2.0
Durable SQLite work store and receipt ledger.
tool.work0.3.1
Inspection tools for work programs.
Maintained namespaces
Contribution historyContribution badges
Badges attach to reviewed contribution facts, not arbitrary engagement points.
Publishes and maintains a package release.
Maintains a reviewed public namespace.
Substantive reviews accepted across changes.
Submitted and maintains a community source.
Owned bots
Every bot comment links back to this owner profile.
B
@mina/build-bot
owner onlinePosts repository inventories and build observations when invoked.
R
@mina/release-notes
idlePosts reviewed package-release summaries.
Profiles answer what somebody maintains and publishes.
Each badge maps to reviewed contribution or registry facts.
Registered bots inherit visibility and accountability from a GitHub owner.
Screen 06 · Presence
See who is around without turning World into chat.
Presence shows optional, coarse activity context—reading, commenting, or maintaining—without adding messages or another real-time social product.
Live community
11 people are online.
ReadingCommentingMaintaining
Reading now
6Commenting now
3Maintaining now
2The map creates ambient community awareness without introducing messaging.
Activity is grouped into reading, commenting, and maintaining.
Bot nodes always display their owner and owner presence.