ADR 0002: Single brand, product taxonomy, pillars, stages and prefix rule

Status

Accepted

Date

2026-09-13

Deciders

Founder, product team

Context

The brand kit fixes the public name Trovensa, the descriptor “Agentic intelligence for drug development.” and the tagline “From evidence to progress.” (direction.json, brand-voice.md). The kit’s internal direction name is never used on any surface. The brief describes four capability areas (discovery investigation, research execution, quality review and traceability, program progress) and names the lifecycle “discovery, preclinical and clinical development, and manufacturing planning”. The kit’s illustrative navigation (brand guide p.11) reads “Evidence · Research plans · Review queue”. The kit names three core messages: “Evidence in context”, “Work with continuity”, “Decisions with a record”. The brand name has no abbreviation, and the copy gate’s prefix rule (site/scripts/check-copy.mjs lines 130-138) flags every occurrence of the prefix not followed by a product name.

Decision

• Products, in this fixed order and all designed: evidence Evidence, plans Plans, review Review, progress Progress. The fourth product was first proposed as “Programs” and renamed to Progress on 2026-09-13 because the tenant scope is a program (ADR 0003); no route or page ever carried the old name.
• Pillars: CONTEXT (“Evidence in context”, evidence), CONTINUITY (“Work with continuity”, plans and progress), RECORD (“Decisions with a record”, review). Titles are the kit’s core messages verbatim; labels are upper-case single words so they never collide with product or stage names.
• Stages (immutable ids): discovery, preclinical, clinical, manufacturing, with titles Discovery, Preclinical development, Clinical development, Manufacturing planning.
• Product prefix: the brand name itself (“Trovensa Evidence” in marketing copy; bare names in the app and docs). words.productPrefixRule = false because the bare brand name legitimately stands alone; the rule would otherwise fail on every sentence that names the company.
• Forbidden words: the two phrases that join the brand name or the word “brand” to the kit’s internal direction name (words.forbidden in forge.config.json; the docs never spell them out). Retired phrases: the four sentences from the kit’s “Avoid” column plus the scaffold placeholder. Vendor words (never in an H1 or hero): AWS, Amazon, Azure, Microsoft, Entra, Google Cloud, Kubernetes, Bedrock, Terraform, PostgreSQL, OpenAI.
• Agent output is called “agent-generated” or “proposed”; the label “AI” joined to “generated” is rejected by the attribution word list and is not used.

Consequences

• forge.config.json, PRODUCT-CONTRACT.md section 1, site/lib/content.ts, web/lib/content.ts, the docs mirror and the deck outline carry the same four products, three pillars and four stages in the same order.
• Every marketing sentence about a capability uses “being designed to”, “intended to” or “would”; status chips show “designed” on every product.
• The brand icons source, modules, review, program identify the products; no new hues are introduced (ADR 0007).

Alternatives considered

• Three products (Evidence, Workflows, Review): folds program tracking into workflows; loses the connected-program view the brief calls out; rejected.
• One product, no sub-products: simplest catalog but a weak marketing grid and no per-product permissions; rejected.
• Prefix “Trov.”: shorter, but not in the brand kit; rejected.
• A six-step research-workflow spine as stages: better for per-experiment records, weaker for program tracking; the lifecycle the brief names was chosen.

Follow-ups

• none