Technical products for work that has to remain inspectable.
Hraness builds deliberately scoped tools across the terminal, browser, and agent workflows. Each product puts a usable result first, keeps the nearest evidence within reach, and states the boundary around what it owns.
| If you need to… | Start here | What you can inspect first |
|---|---|---|
| Coordinate local coding-agent work and repository gates | HRA | The task, exact tree, check, and delivery receipt |
| Capture web sources or run a typed provider operation | Wrench | The normalized record, archived media, or bounded operation result |
| Generate or edit media from a CLI, SDK, MCP server, or Agent Skill | Atet | The produced artifact and the interface that made it |
| Turn a Markdown vault into searchable, linked knowledge | KB | A finished query with the notes and relationships behind it |
| Drive a frontend through repeatable browser scenarios | Direct | The scenario, browser observation, and verification result |
| Compose a MIDI loop with a person or agent | Soundfish | A self-contained, content-addressed composition URL |
The portfolio also includes focused web products for life perspective, research editions, sound and sleep, public dataset exports, and model comparison.
The interfaces differ, but the reader path stays familiar:
- Result — show a real output, artifact, or state before explaining the architecture.
- Working model — name the few steps and invariants that produce it.
- Interfaces — make the CLI, package, website, API, and agent entry points agree about the same product.
- Evidence — keep sources, receipts, tests, or deterministic observations close to the claim they support.
- Boundary — say what stays local, what is hosted, what can have external effects, and what the product does not promise.
That sequence is a design system for trust, not a claim that every product has the same visual identity.
- Product sites are the shortest path to a result.
- Public repositories own source, releases, contribution paths, and technical contracts for open products.
- Agent-facing documents and machine-readable routes mirror the same stable facts when a product supports them.
- Hraness.com is the portfolio index and links each product to its canonical surface.
Individual product pages state their own account, privacy, cost, storage, network, and availability boundaries. Do not infer one product's guarantees from another's.
Open the product that matches the job, reproduce its first proof, and use its repository for issues or contributions. Maintainers can use the shared README guidelines to keep repository and website stories aligned.
