Start with evidence intake.
The product does not begin with a blank-page site editor. It begins by collecting proof and making that proof usable.
Back to works
02.03.06 — jaro.works
Concept draft2026 · Professional presence system
jaro.works
A portfolio should not go stale the moment it ships. It should behave like a managed public presence with memory, evidence, and editorial control.
Role
Founder/product framing, workflow design, and editorial model.
Audience
Operators, product leaders, builders, and independent professionals whose work changes faster than their public story.
Presence ops
AI-assisted01
Capture
Screenshots, notes, launches
02
Position
What this proves
03
Review
Human editorial pass
04
Publish
Portfolio update
Primary artifact
Professional presence workflow
01 — Context
What this is really about.
jaro.works is the next product story to draft. The premise: professional presence is operational work. Good public positioning depends on collecting evidence, understanding what it proves, updating the story, and publishing only after review.
Product Question
Can AI help maintain a professional presence while keeping the human responsible for public claims?
02 — Problem
The user pressure.
Professionals accumulate proof in projects, screenshots, launches, writing, and notes, but the public story rarely keeps up. Static portfolios decay because maintenance requires synthesis, taste, and time.
03 — Evidence
What the artifacts prove.
Workflow
The important artifact is the operating loop.
The first artifact is a storyboard: capture, position, review, publish. Screenshots matter only if they make that loop clear.
Trust
AI assists. It does not impersonate.
The product needs a clear review state. A professional presence tool becomes risky if it publishes confident language without the user's judgment.
Memory
Evidence needs to stay connected to claims.
The system preserves why a project, screenshot, article, or result supports a specific public claim.
04 — Product Judgment
Product decisions.
Keep positioning editable.
AI can propose a story, but the user owns the public claim. The story needs review, revision, and rejection states.
Make maintenance the product.
The durable value is not a one-time portfolio export. It is the ongoing workflow that keeps public presence aligned with real work.
05 — Evidence Plan
What is still missing.
Draft the first storyboard and create wireframes for evidence intake, positioning review, and publish approval.
Evidence intakePositioning mapReview queuePublish workflow
Open Questions
01
What evidence types should the product support first?
02
How should the user verify that a claim is supported by real proof?
03
What gets automated, and what must always stay human-reviewed?