Capture the rough meeting context
The page starts with the user-facing workflow: collect the messy notes and preserve the context needed for a useful handoff.
Static AgentSite · product-cockpit recipe · no-payment mode
Turn messy meeting notes into a clear action handoff
Harbor Notes helps visitors understand how a lightweight notes workflow could capture rough meeting context, clarify decisions, and prepare next actions for review without pretending to be a live product dashboard.
The page explains the user-facing workflow first, then gives reviewers the operating context, repo-local proof, and approval boundaries needed to evaluate the next step safely.
Operating context
What decision this page helps visitors make
A static product-cockpit page that explains the meeting-notes-to-next-actions workflow and gives reviewers proof artifacts and safe boundaries.
Create a restrained, premium static landing page for independent consultants and fractional operators who capture messy meeting notes, extract decisions, and hand off a clear next-action log.
Audience named in the brief
Built for the people who need the workflow explained clearly.
- Independent consultants who leave meetings with scattered action items
- Fractional operators maintaining client-facing decision logs
- Solo founders testing whether a lightweight notes-to-next-actions workflow deserves a real product
Cockpit panels
Status, workflow, proof, and constraints in one scan.
Extract decisions and owners
It then frames how decisions, owners, and open questions could be separated from the raw notes for a cleaner review.
Hand off a next-action log
The final workflow panel shows a safe next-action log that can be reviewed, corrected, and maintained through repo-local contracts and QA.
Proof artifacts
Evidence a future maintainer can verify.
Site contract
.agent/site.contract.yaml records the mission, audience, required sections, allowed claims, and approval-required boundaries.
QA commands
npm run qa and npm run qa:full verify contracts, claims, links, build output, and visual behavior locally.
Recipe registry
.agent/recipes/product-cockpit documents the static-safe cockpit pattern and acceptance criteria.
Boundaries
What is not claimed here.
Not claimed: fake customer quoted endorsements.
Not claimed: fake metrics.
Not claimed: live telemetry.
Approval required: Adding analytics, cookies, tracking pixels, or third-party forms.
Approval required: Adding payment links or enabling payment mode.
Approval required: Making customer, benchmark, revenue, conversion, or availability claims.
Safe next step
Inspect the cockpit
Use the cockpit panels, repository contracts, and QA commands before changing claims, scope, payments, analytics, or deployment settings.