Haynechi
Haynechi Index Understand where you stand in AI Search before competitors own the prompt map.

Engineering

Technical model, visible at the surface.

Haynechi keeps the public site fast, the intake path scoped, and the product objects ready for a governed workspace.

Static Public layer
Edge Pilot intake
Objects Workspace model
Boundary App controls
System docs Trust packet

Architecture System

Technical credibility starts with clear boundaries.

Fast public pages, scoped intake, product objects, and app-layer controls stay separated so evaluators can see what is live today and what belongs in the governed workspace.

Read system docs
System Layers5 states
Public layer

Static routes, crawler files, metadata, headers, redirects.

live
Primitive layer

Tokens, panels, rows, states, responsive grids.

live
Edge intake

Validated pilot requests become scoped briefs.

edge-ready
Content path

Schema-backed content and route contracts.

planned
App boundary

Accounts, roles, audit, integrations, retention.

app boundary
Product PrimitivesObject model
Prompt object

engine, region, stage, competitor, owner, review state

Answer snapshot

answer, sources, position, sentiment, omissions, confidence

Source record

URL, type, freshness, authority, correction path

Agent run

template, inputs, guardrails, approval, shipped work

Readiness PathPublic to app
01 Public surface

Category, product model, trust posture, pilot offer.

02 Pilot intake

Buyer context becomes a scoped request.

03 Workspace model

Prompt, answer, source, agent, owner, proof.

04 Application path

Typed primitives, analytics policy, customer controls.

Reviewer LensesWho trusts it
Buyer

Evidence to owner-ready work.

Operator

Object, state, owner, approval, readout.

Technical

Public layer, edge intake, model, app boundary.

Executive

Maturity without inflated proof.

System BoundariesExplicit scope
Workspace boundary

Accounts, SSO, integrations, and admin stay app-layer.

Data minimization

Pilot scope starts with market context and approved sources.

Integration discipline

Syncs use scoped fields, labels, owners, destinations.

Migration discipline

Public pages stay fast while primitives move to schemas.

Engineering Engineering note

Building An Agent Runtime For Supervised Marketing Work

The primitives behind templates, nodes, approvals, runs, and measurable outputs.

Signal Inputs Run lineagewhich evidence, constraints, and prompts shaped the outputApproval statereview ownership and publication readiness
Workspace Outputs Run modelNode graphArtifact ledger
Proof boundary

Technical notes keep implementation state, app boundary, data contract, and validation path separate.

Open note
Engineering Engineering note

Classifying AI Crawlers Without Losing The Signal

How Haynechi normalizes user agents, edge logs, freshness windows, and downstream attribution.

Signal Inputs Bot classverified, likely, unknown, blocked, or first-party monitoringFreshness windowcrawl timing around source updates
Workspace Outputs Crawler taxonomyFreshness reportSource access audit
Proof boundary

Technical notes keep implementation state, app boundary, data contract, and validation path separate.

Open note
Engineering Engineering note

Designing A Prompt Graph For Category Intelligence

What it takes to cluster, score, and monitor prompts that change weekly.

Signal Inputs Cluster shapeintent, entity, stage, modifier, and regionAnswer statevisibility, sentiment, citations, and competitor framing
Workspace Outputs Prompt graph schemaCluster scorecardAnswer ledger join
Proof boundary

Technical notes keep implementation state, app boundary, data contract, and validation path separate.

Open note

Stack Decisions

Built static first, with a clear path to a governed workspace.

The public layer stays fast and mostly static. The product model is structured around prompts, answers, sources, agents, and proof events so workspace controls can move into a governed app boundary when customer data enters the system.

implemented

Static marketing layer

Node-generated HTML keeps the public surface fast, inspectable, and Cloudflare Pages-ready with crawler guidance and deployment metadata generated alongside routes.

implemented

Structured content collections

Feature, solution, resource, legal, and architecture content is represented as data before being rendered into routes.

implemented

Product primitive library

Reusable sections for agents, answer maps, operating consoles, proof boards, article rails, and pilot offers keep detail consistent.

implemented

Contact intake function

Cloudflare Pages Function validates submissions, filters honeypot traffic, and can forward to CRM or webhook destinations.

future app

Authenticated workspace

The pilot workspace sits behind a separate app boundary for accounts, audit logs, exports, SSO planning, and data retention controls.

scoped

Analytics and CRM sync

PostHog or Plausible plus HubSpot, Salesforce, or warehouse sync connect after production tracking policy and buyer-approved destinations are defined.