Documentation

TrustStone helps Summerfest founders get pitch-ready. Founders, coaches, community partners, and admins each get their own workspace, reached through a personal claim link.

In Summerfest the person who helps a founder is called a coach (not a mentor). The left menu only shows what your role needs.

Anywhere you see a question-mark button, click it to jump straight to the part of this guide that explains that screen. The Releases page lists everything that has changed, newest first.

Step 1: Open your claim link and confirm your basic information. Step 2: Complete the founder diagnostic. It asks a few quick competition-context questions, then has you rate yourself on the six Summerfest rubric areas. Step 3: You are matched with a coach. Step 4: Meet with your coach, and after each session do the short check-in.

The diagnostic is short by design: a three-question context section, the six rubric self-ratings with brief evidence, and a few questions about how you work. Your pathway tier is worked out from your six rubric scores.

You only ever see the six Summerfest rubric areas. You will not see internal signal scores.

Step 1: Open your claim link and confirm your profile. Step 2: Complete the coach diagnostic: it confirms your background, captures your expertise (including the Summerfest rubric areas you are strongest in), and asks how you coach. Step 3: You are matched with founders. Step 4: After each session, complete the post-session capture.

You are a coach in Summerfest, not a mentor. Add your phone number in Settings so you receive session alerts and reminders.

Your post-session capture takes under five minutes and is the most important thing you do between sessions: it is how the system and Admin see how each founder is tracking toward pitch day.

The community partner diagnostic is a short onboarding form. It takes 8 to 12 minutes and needs no account or login.

You enter your organization details, pick your sponsor type, answer a short branched set of questions for your sponsor type, and then a shared outcomes section everyone completes. On submit, your information becomes your Community Partner card and Admin is notified.

Control Room is the admin view. The top tiles show live counts (Founders, Coaches, Community Partners, Architects) and Flagged sessions. Click a count tile to filter the roster to that role.

Tile behavior is quiet on purpose: hover lifts the tile with a soft shadow, and the selected tile shows a clean outline ring instead of a color fill.

Matching is admin-led; agent suggestions are secondary. Flagged signals surface sessions where a side flagged the relationship, sentiment was negative, or a coach marked a founder as urgent for pitch day.

On the Invites page pick the role, enter the person’s name and email, choose routing tags, and create the invite. The selected role card shows a clear ring so it is always obvious which role you are creating.

Each invite gives a claim link and QR code. The person claims the account, confirms their basic info, and lands on their role dashboard.

A Relationship Card is scoped to one coach-founder pairing and the sessions within it. It holds the session timeline, the health signal, and the Signal Matrix for that relationship.

Founder onboarding baseline scores live on the Company Profile. Per-session re-assessments live on the Relationship Card: the founder_reassessment array (founder self-ratings) and the coach_assessment array (coach ratings), kept separate so the gap between them can be measured.

In Summerfest the Signal Matrix is shown as the six pitch-rubric areas: Creativity, Traction, Opportunity, Team, Goodness, and Q&A Readiness. Founders only ever see the rubric.

Internally the system still keeps the standard eight signal dimensions. The internal mapping, taken from the canonical Founder and Coach diagnostics’ per-dimension internal mappings (the Companion Update, which would otherwise own this table, is still outstanding), is: Creativity = Problem Validation + Product Readiness; Traction = Customer Acquisition + Revenue Signal; Opportunity = Customer Clarity + Fundraising Readiness; Team = Team & Hiring; Q&A Readiness = Founder Execution. Goodness is a standalone dimension with no standard-eight equivalent and shows a neutral placeholder until its dedicated field is wired.

The radar is shown in neutral greyscale to match the clean site standard.

Discovery Notes record a friction moment and what happened. The Session Context field is limited to Pitch for Summerfest, since the pitch is the competition’s only session function.

Each note records the moment, the session context, an outcome signal, and the reasoning behind it.

After a session both the founder and the coach are prompted independently, 5 to 10 minutes after the scheduled end time. Neither side sees the other’s answers. Only Admin sees both. The per-dimension gap between coach and founder ratings is computed automatically, and a gap of 2 or more points on any single dimension is flagged for Admin.

Founder Post-Session — a light two-minute check-in, no open text. Section A is a quick session reflection (three multiple-choice questions). Section B re-rates the same six Summerfest rubric dimensions (Creativity, Traction, Opportunity, Team, Goodness, Q&A Readiness) on a 1–4 scale. Responses are stored in the founder_reassessment array on the Relationship Card with a timestamp and session number — never on the Company Profile — and compared to the onboarding baseline to show progress.

Coach Post-Session — a four-section capture, under five minutes. A: session confirmation (did it happen, was the deck shared, which session number). B: rubric assessment — rate the founder on each of the six dimensions (1–5) with one short coaching note per dimension. C: commitment and follow-through — check the prior commitment and set the next one (shown to the founder). D: pitch-day readiness signal — overall tracking, including an Urgent option that escalates to Mike, plus the single most important thing to improve before pitch day. Responses are stored in the coach_assessment array on the Relationship Card.

Build status: the two captures above describe the canonical specification (Founder/Coach Post-Session Capture specs plus the Companion Update data model, delivered 2026-05-18). They are not yet implemented in-system — the interim generic session-feedback prompt still runs until the canonical captures and their Relationship Card array storage are built.

Founder Diagnostic (built): the five-section canonical instrument runs in the founder claim flow — profile validation, a short competition-context section, the six Summerfest rubric self-assessment dimensions with brief evidence, founder beliefs and working style, and value exchange. The standard eight-signal section is retired for Summerfest and replaced by the six rubric dimensions; pathway tier and the bottleneck dimension are computed from the rubric scores.

Coach Diagnostic (specified, not yet built in-system): professional identity (confirmed, not retyped), standard expertise plus the Summerfest rubric expertise layer, working style, communication, capacity and commitment, and value exchange. Q&A Readiness is a derived field for coaches, not self-rated.

Community Partner Diagnostic (specified, not yet built in-system): organization identity, sponsor type with silent branch routing, the branched questions for that sponsor type, a shared outcomes section, and submission. No account required.

Build status: only the Founder Diagnostic is live. The Coach and Community Partner question sets are documented from the canonical specs but are not yet implemented in TrustStone. The Summerfest Companion Update — the data-model, translation, gap-agent, trigger, and export source of truth — was delivered 2026-05-18 and is now authoritative; the founder submit still persists through the existing questionnaire envelope with deterministic scoring stand-ins, and is being brought to the Companion Update data model as the remaining build proceeds.

Settings holds your editable profile: name, bio, title, organization, location, phone number, and LinkedIn. The phone number is used for session alerts and reminders, including post-session prompts to coaches.

Email cannot be changed from Settings. Notification preferences and AI-helper consent are also managed here.

The Feedback Capture panel records what you do, lets you tag a specific element, and attach a marked-up screenshot. Submitted feedback is stored with the action trail and routed for review.

This is the channel the product team reads between sessions. Describing what you expected versus what happened, plus a screenshot, is the most useful form.

The Releases page is the changelog. Each release lists features, improvements, and fixes, with links into the relevant documentation section.