Skip to route content
Hara
Review publication fields
Implemented
packages.package@2.2.0 packages.release@2.2.0 packages.namespace@2.2.0 packages.maintainer@2.2.0 packages.compatibility@2.2.0

Package and namespace reference

Packages and namespaces are versioned registry records.

A package is a versioned distribution unit containing artifacts and one or more namespaces. A namespace is a named collection of Vars and public symbols. Search results retain the exact coordinate, release, ownership, compatibility, maintenance, artifact, and provenance records needed to evaluate a dependency.

View a package record Review publication fields View maintainer records
Content contract
5 hara.packages@2.2.0 types
Fixture packages
6 exact coordinates
Namespaces
18 registry references
Registry questions
6 recorded answers
Registry lookupExact match
Package coordinatehara/std.typed2.4.1 · stable
package:hara/std.typedcontainsnamespace:std.typed
Release revision
6a7f813ca41d227e
Artifact digest
sha256:8ad194f1764a…
Publisher
identity:github:hoebat
Compatibility
3 verified · 1 partial

Registry search

Search by coordinate, namespace, purpose, or capability.

Filters expose domain, runtime, stability, licence, and compatibility independently. Every result retains its exact release and maintenance state.

Registry ready

Search, filters, exact identities, and release facts are current at the shown registry revision.

registry 71c4ef92
Packagehara/std.typed2.4.1

Typed schemas and coercion

Canonical schema, validation, coercion, and typed data contracts for Hara programs.

stableverifiedApache-2.0
std.typedstd.typed.schemastd.typed.coerce+1
Runtimes
jvm · rust · wasm · node
Dependants
128
Updated
Release revision
6a7f813ca41d227e
Packagehara/std.work0.9.0

Durable work algebra

Replayable work, checkpointed steps, capabilities, queues, timers, and durable receipts.

previewpartialApache-2.0
std.workstd.work.runtimestd.work.backend
Runtimes
jvm · rust · node
Dependants
47
Updated
Release revision
d2b9f02674aa51c8
Packagehara/code.maven4.1.3

Artifact and dependency resolution

Exact Maven coordinate resolution, repository policy, lock data, and artifact verification.

stableverifiedEPL-2.0
code.mavencode.maven.packagecode.maven.repository
Runtimes
jvm · node
Dependants
212
Updated
Release revision
87bc4109e3a5f712
Packagehara/ui.canvas0.6.2

Canvas and live visual fields

Canvas scenes, deterministic animation controls, observation streams, and portable visual forms.

previewpartialMIT
ui.canvasui.canvas.fieldui.canvas.observation
Runtimes
wasm · node
Dependants
18
Updated
Release revision
a119e8f742dccb30
Packagegreenways/hestia-client0.3.0

Signed document storage client

Key-scoped storage, signed version chains, room access, and receipt-aware document retrieval.

previewunknownApache-2.0
hestia.clienthestia.client.roomhestia.client.receipt
Runtimes
jvm · node · wasm
Dependants
6
Updated
Release revision
359de19a764bc08f
Packagehara/legacy.stream1.8.7

Legacy stream adapters

Compatibility-only stream aliases retained while consumers migrate to explicit work and channel contracts.

deprecatedpartialEPL-2.0
legacy.streamlegacy.stream.adapter
Runtimes
jvm
Dependants
31
Updated
Release revision
501ce18e7eaa0bf4

Package detail

Purpose first. Exact release facts beside it.

The package record explains what a coordinate is for; the release record proves which version, source, artifacts, namespaces, compatibility evidence, and publisher signature were published.

Package coordinate

hara/std.typed

Canonical schema, validation, coercion, and typed data contracts for Hara programs.

Available release2.4.1release:std.typed:2.4.1:6a7f813ca41d227e
Install projectionhara packages install hara/std.typed@2.4.1 --digest sha256:8ad194f1764a5f0a

Illustrative CLI projection. The package runtime owns executable install syntax and verification.

Open install guide
Available releaseArtifact, signature, compatibility evidence, and exact registry revision are available.

No release or resolver findings in this state.

Install allowed
Yes, with exact verification
Receipt
release:std.typed:2.4.1:6a7f813c
Namespace inventory

4 exact stewardship boundaries

Inspect namespace detail →
Namespacestd.typednamespace:std.typed
Status
active
Public forms
18
Introduced
2.0.0
Namespacestd.typed.schemanamespace:std.typed.schema
Status
active
Public forms
31
Introduced
2.0.0
Namespacestd.typed.coercenamespace:std.typed.coerce
Status
active
Public forms
14
Introduced
2.1.0
Namespacestd.typed.validatenamespace:std.typed.validate
Status
active
Public forms
22
Introduced
2.0.0
Compatibility matrix

Target claims retain evidence.

Verify all evidence →
TargetVersionStateEvidence
JVM21verifiedcompat:std.typed:2.4.1:jvm21:pass
Rust evaluator0.9verifiedcompat:std.typed:2.4.1:rust09:pass
Browser/Wasm0.9partialcompat:std.typed:2.4.1:wasm09:partial
Node22verifiedcompat:std.typed:2.4.1:node22:pass
Dependencies3
hara/std.lib^4.2 → 4.2.3sha256:f3042a8c
hara/std.string^3.7 → 3.7.1sha256:ab117d92
hara/code.query^2.1 → 2.1.0sha256:9ce54a21
Reverse dependencies3 shown
hara/tool.metaspec1.7.0verified
hara/tool.lint3.2.1verified
greenways/hestia-schema0.4.0partial
Use and inspectExamples hand off to the owning product.

Namespace detail

A namespace is stewardship, not a package card subsection.

Namespace identity, ownership, public forms, aliases, conflicts, migrations, and runtime availability remain distinct from the package and release that currently distribute it.

Namespace identity

std.typed

Public schema construction, validation, and coercion forms distributed by hara/std.typed.

activeintroduced 2.0.0namespace:std.typed
9 public formsOpen canonical reference
Public API

Registered forms and version boundaries

Deprecated forms remain visible with their introduction and migration evidence.

FormKindCategoryIntroducedDeprecated
std.typed/schemafunctionSchema construction2.0.0—
std.typed/optionalfunctionSchema construction2.4.0—
std.typed/unionfunctionSchema construction2.4.0—
std.typed/checkfunctionValidation2.0.0—
std.typed/explainfunctionValidation2.1.0—
std.typed/valid?predicateValidation2.0.0—
std.typed/coercefunctionCoercion2.1.0—
std.typed/coercion-receiptfunctionCoercion2.4.0—
std.typed/coerce-nilfunctionCoercion2.1.02.4.0
Exact exampledocs.live-example + packages.namespace
Run in Playground →
(require '[std.typed :as t])

(def profile
  (t/schema {:name :string
             :email (t/optional :string)}))

(t/check profile {:name "Ada"})
Package hara/std.typed@2.4.1Namespace revision namespace:std.typed:91c8347e2ac05bb1
Runtime availability

Distribution does not imply parity.

Each target retains the exact package version and availability state.

JVM2.4.1available
Rust evaluator2.4.1available
Browser/Wasm2.4.1partial
Node2.4.1available
Aliases2
typed→std.typedsupported
schema/check→std.typed/checkmigrationdeprecated 2.3.0
Conflicts2
checktool.metaspec

Use qualified symbols; no registry collision exists.

documented
schemastd.schema

Legacy alias redirects to std.typed/schema through 3.0.

migration
Migration paths2
std.schema→std.typed2.0.0namespace-migration:std.schema->std.typed:2
schema/check→std.typed/check2.3.0symbol-migration:schema.check->std.typed.check

Publish workflow

Author release intent. Let registries control identity and proof.

Release and migration notes are editable. Package coordinates, namespace ownership, version, maintainers, compatibility evidence, artifact digests, lifecycle state, revision, and publication receipt stay controlled.

packages.release@2.2.0

std.typed 2.5.0 beta 1

Adds typed protocol projections and checker evidence for cross-runtime schema boundaries.

Draft
Author-controlled metadata

Human explanation remains portable.

Raw front matter
schema: hara.packages
schemaVersion: 2.2.0
contentType: packages.release
title: std.typed 2.5.0 beta 1
summary: Adds typed protocol projections and checker evidence for cross-runtime schema boundaries.
releaseNotes: |
  Promotes protocol projection and explicit mismatch facts into the shared typed contract.
migrationNotes: |
  No source break for 2.4 consumers; new projection receipts are opt-in.
Version and compatibility declaration2.5.0-beta.1
Package
package:hara/std.typed
Language range
>=0.9 <1.0
Runtime targets
JVM 21 · Rust evaluator 0.10 · Browser/Wasm 0.10 · Node 22
Namespace inventory4
namespace:std.typednamespace:std.typed.schemanamespace:std.typed.coercenamespace:std.typed.validate
Artifact inventory

Every artifact retains kind, size, and digest.

4 artifacts
PathKindSizeDigest
dist/std.typed-2.5.0-beta.1.harasource archive184 KiBsha256:11d3a86bf271
dist/std.typed-2.5.0-beta.1.jvm.jarJVM artifact412 KiBsha256:286c1a5e30b2
dist/std.typed-2.5.0-beta.1.wasmWasm artifact238 KiBsha256:f1cc72d05e9a
dist/reproduction.jsonreproduction manifest8 KiBsha256:9e4b60b119f2
Build and validation

Exact checks before signing.

passContract validation

hara.packages@2.2.0

metadata
passNamespace ownership

4 of 4 exact stewardship records

namespaces
passDependency lock

12 direct and transitive artifacts verified

dependencies
passJVM compatibility

214 checks

jvm
passRust evaluator compatibility

208 checks

rust
warningBrowser/Wasm compatibility

2 observation tests require review

wasm
pendingPublisher signature

identity:github:hoebat

signature
Registry listing preview

std.typed 2.5.0 beta 1

Preview only

Adds typed protocol projections and checker evidence for cross-runtime schema boundaries.

hara packages install hara/std.typed@2.5.0-beta.1 --digest sha256:11d3a86bf271
Namespaces
4
Artifacts
4
Compatibility
4 declared targets
Source fence
git:77a016d2f9be481c
Draft

Author-owned release and migration notes are editable. No release identity exists.

Author fields
Editable in a new draft
Receipt
No durable receipt yet

Maintainer surfaces

Action queues explain scope, owner, evidence, and consequence.

Releases, namespace ownership, migrations, dependency breakage, contributor review, and owned automation share one package context without collapsing their distinct authorities.

Package operations

Maintain exact releases and stewardship.

Popularity signals are intentionally absent from the action queue.

Current releases3stable · preview · historical
Owned namespaces4all stewardship current
Pending reviews2compatibility + ownership
Dependency alerts31 breaking · 2 advisory
Awaiting action

4 evidence-backed items

reviewrelease
2.5.0-beta.1 awaits Wasm review
Responsible identity
identity:github:reviewer-kappa
Evidence
submission:std.typed:2.5.0-beta.1:77a016d2
requestnamespace ownership
Delegate std.typed.coerce review scope
Responsible identity
identity:github:contributor-lambda
Evidence
ownership-request:std.typed.coerce:12
planningmigration
Complete implicit nil coercion removal plan
Responsible identity
identity:github:hoebat
Evidence
migration-plan:std.typed:nil:3
breakingdependency
code.query 3.0 removes legacy selector alias
Responsible identity
identity:github:hoebat
Evidence
compat-alert:code.query:3.0:std.typed
Contributor and reviewer activity

Profile evidence links back to exact package work.

Inspect provenance →
IdentityActionResultEvidence
identity:github:contributor-lambdaproposed typed protocol projectionacceptedcontribution:std.typed:489
identity:github:reviewer-kappareviewed Rust evaluator compatibilitypassreview:std.typed:rust010:17
identity:github:hoebatpublished 2.4.1publishedpublication:std.typed:2.4.1:6a7f813c
User-owned release bots

Automation remains attached to accountable owners.

An absent owner can pause policy-sensitive actions without erasing prior receipts.

BOTtyped-releaseavailable

Build, sign proposal, and attach reproduction manifest

Verified owner
identity:github:hoebat
Owner presence
Present
Capabilities
build · check · propose
Last receipt / policy
bot-run:typed-release:881
BOTcompat-watchpaused-owner-away

Open compatibility alerts from exact registry changes

Verified owner
identity:github:reviewer-kappa
Owner presence
Away
Capabilities
read registry · open alert
Last receipt / policy
bot-policy:compat-watch:5

Trust and provenance

Six questions should be answerable without trusting the page.

Each answer names its authority and evidence. The interface composes registry facts; it does not become a second package, namespace, identity, compatibility, or receipt registry.

01

Who published this package?

identity:github:hoebat

Authority
Identity registry
Evidence
publisher signature + publication receipt
02

Which revision and artifacts were published?

release:std.typed:2.4.1:6a7f813ca41d227e

Authority
Release registry
Evidence
git:941ad1a87e2c46b3 · sha256:8ad194f1764a5f0a4c9f0a16dd2db49e8a9f309ab3c7ca1cc60bc081766a34d2
03

Which namespaces are included?

4 exact namespace references

Authority
Namespace registry
Evidence
namespace:std.typed · namespace:std.typed.schema · namespace:std.typed.coerce · namespace:std.typed.validate
04

Which runtime targets are supported?

JVM 21: verified · Rust evaluator 0.9: verified · Browser/Wasm 0.9: partial · Node 22: verified

Authority
Compatibility registry
Evidence
compat:std.typed:2.4.1:jvm21:pass · compat:std.typed:2.4.1:rust09:pass · compat:std.typed:2.4.1:wasm09:partial · compat:std.typed:2.4.1:node22:pass
05

What changed from the previous version?

Promotes generic schema extensions and explicit coercion receipts.

Authority
Release note + migration relation
Evidence
migration:std.typed:2.3-to-2.4:4d12a7c9
06

How can the release be verified or reproduced?

Resolve the source revision, lock, artifact manifest, digests, checks, and publisher signature.

Authority
Package registry
Evidence
reproduction:std.typed:2.4.1:manifest:58d19c7a
Reproduction chain

Resolve inputs, rebuild artifacts, compare evidence.

Reproducible fixture
Packages application owns

Discovery, comparison, install projection, publish composition, maintainer queues, state presentation, and links into Docs, Playground, Specs, and World.

Registries own

Package coordinates, namespace stewardship, versions, maintainers, compatibility evidence, artifact digests, lifecycle decisions, signatures, and durable receipts.

Runtimes own

Actual dependency resolution, artifact download, installation, environment checks, execution, reproduction, and install-attempt receipts.

Ownership and adoption

The interface reads registry records; it does not define them.

A package service may use these specimens while keeping coordinates, namespace stewardship, releases, artifacts, compatibility results, lifecycle decisions, signatures, and receipts in authoritative registries.

Visual Language

Shell, tables, filters, forms, status, identity labels, focus, responsive behaviour, receipts, and unavailable-state presentation.

Packages application

Search, comparison, install projection, package and namespace navigation, publication forms, maintainer queues, and cross-route links.

Package and namespace registries

Coordinates, stewardship, versions, maintainers, artifacts, compatibility evidence, lifecycle decisions, signatures, and receipts.

Resolver and runtimes

Dependency resolution, download, verification, installation, execution, environment compatibility, reproduction, and attempt receipts.

Docs, Playground, Specifications, and World

Version-aware guidance, execution, formal contracts, and public discussion retain separate navigation and authority.

Review the front-matter contract, component reference, workflow-state reference, Docs handoff, Playground handoff, and V2-PACKAGES.md before adoption. This fixture exposes 5 hara.packages types and no live registry records.