The shared mechanics that apply to every template in the founding suite: what a template is, what the cohort work between prompts does, how to run the prompts across different deep research platforms, and the evidentiary discipline every template requires.

What a template is

A template in this suite is a structured three-prompt sequence for use with a deep research AI platform, with cohort review between prompts.

The AI does the research and drafts the documents. The cohort makes the selections, resolves the tensions, and holds the commitments. The template is the coordination instrument that keeps the two in phase.

Every template in the suite produces three final documents in Prompt 3: a short formal Statement or Definition, a long referential Evidence Pack or Atlas, and a short co-signed Compact or Charter. Reader learns the pattern once and recognizes it across all four templates.

Prerequisites

  • A coordinator who convenes the cohort and runs the prompts.
  • A cohort. At minimum, a coordinator and two to five founding participants who have committed to the founding work. The first template’s Founding Compact formalizes this.
  • A decision-making form the cohort agrees to work within. Set during the first template. Governs the between-prompt cohort work in every subsequent template.
  • Access to a deep research AI platform (ChatGPT Deep Research, Claude Research, Perplexity Deep Research, Gemini Deep Research, or an equivalent).
  • The source documents each template lists as prerequisites.

For the first template, the cohort is not yet formalized. Use Prompt 1 as a working draft to bring to the cohort once assembled.

The between-prompt cohort work

Every template in the suite has cohort review steps between its prompts. Between Prompt 1 and Prompt 2, the cohort reviews the AI’s first pass and makes selections. Between Prompt 2 and Prompt 3, the cohort reviews the evidence pack and resolves the tensions it has surfaced.

The cohort work cannot be delegated to the AI. Three reasons:

The AI does not have the cohort’s local knowledge. A boundary that looks right on ecological grounds may cut through a heritage territory the cohort knows about but the AI does not. A counterparty the AI names as a plausible buyer may already have refused an approach from a peer BioHub, and the cohort knows why.

The AI does not have standing to commit the cohort. The Compacts are co-signed. Only the cohort can co-sign them. The AI can draft; it cannot commit.

The AI does not have the relationships the resolutions depend on. Ecological-cultural reconciliation where indigenous or first-nation authority is involved depends on consent work the cohort does with the authorities concerned. Multi-BioHub coordination depends on relationships the cohort holds with adjacent BioHubs. Neither is delegable.

The cohort work operates under the decision-making forms established in the Founding Compact. Where the cohort does not yet have the standing or the relationships to resolve a tension, the template’s Prompt 3 is paused until the necessary work is done.

The between-prompt work is often the longest part of the template. The AI’s prompts run in minutes. The cohort’s review may take days or weeks. This is a feature, not a delay.

Cross-platform notes

The prompts are written for portability across ChatGPT Deep Research, Claude Research, Perplexity Deep Research, and Gemini Deep Research.

Claude and ChatGPT accept long submissions with attached documents. Submit the full prompt with prerequisites attached.

Perplexity works best with tighter, more focused queries. Condense the prerequisite documents into a single summary and paste it inline before the prompt where full attachment is not possible.

Gemini handles structured briefs well and supports document uploads through its research mode.

Where a platform cannot carry context across sessions, manually attach the outputs of previous prompts to the subsequent submissions.

Prompt 3 in every template produces three separate documents with a combined length that may exceed some platforms’ output limits. Where a platform cannot produce all three in a single response, split Prompt 3 into three separate submissions (3a, 3b, 3c), each carrying the Prompt 2 evidence pack as an attached input.

Prompt 2’s evidence pack is the largest output in every template. Where the platform imposes tight output limits, produce it in structured sections and assemble them separately.

Evidentiary discipline

Every template applies the same tagging system to claims.

IC (Independently Corroborated). Claims supported by cited sources outside the BioHub’s own documents. Every citation carries source name, publication date, publisher or institution, and a direct quote or paraphrase locating the claim.

MS (Mission-Sourced). Claims drawn from the preceding template outputs or other cohort documents.

TBV (To Be Verified). Claims that are plausible but need a subsequent prompt or specialist verification to substantiate. Where a source is behind a paywall or otherwise not verifiable in real time, mark it TBV and note the citation for later verification.

Structural inferences (claims of the form “this pattern implies that outcome”) are explicitly labeled as inference. They are not attributed to source authors.

Fabrication is out of scope. If a plausible source cannot be found, mark the claim TBV. If a domain availability check cannot be performed in real time, mark it TBV. If a trademark search cannot be performed, mark it TBV. If a citation would need to be invented, do not include the claim.

The three-document output pattern

Every template’s Prompt 3 produces three documents. Reader learns the pattern once and recognizes it across the suite.

Statement or Definition. Short, formal, foundational reference document. Five to ten pages. Prose-forward, formal register. Used to introduce the BioHub, the BioRegion, the value proposition, or the alignment to counterparties, funders, peer BioHubs, and instrument parties.

Evidence Pack or Atlas. Long, structured referential document. Twenty-five to sixty pages depending on the template. Reference register. Structured for section-by-section reference use. Used to answer due diligence questions, prepare specific tenders, brief participants, and structure specific coordination work.

Compact or Charter. Governance and commitment document. Five to ten pages. Commitment register. Co-signed by the cohort. Used to convene formal coordination relationships and to demonstrate governance standing.

The three documents are not interchangeable. Each has a distinct purpose and audience. None of them is promotional. None closes with a call to action.

Each document ends when its content ends. No closing summary. No restatement of what was just said.

Handoff between templates

The nine outputs of the three establishment templates are prerequisite inputs to the fourth. Attach all nine (alongside the target instrument documentation) to the first prompt of the Bankable Service Alignment Template.

Within the establishment suite, each template’s outputs feed the next. The BioRegion Establishment Template inherits the anchor location, cohort structure, and purpose statement from the Identity Statement; the global BioHub field baseline, intellectual lineage, and adjacent BioHubs from the Field and Lineage Positioning; and the cohort structure, decision-making forms, multi-BioHub coordination protocols, and custodial and consent principles from the Founding Compact. The BioConomy Value Proposition Template inherits from all six preceding outputs.

Preserve the vocabulary and conventions established across the suite. Where a term appears in one template, it appears in the same sense in all subsequent templates.

The three-layer coordination stack

Once all four templates have been run, the BioHub sits inside a three-layer coordination stack. The Founding Compact governs BioHub-level coordination. The BioRegion Charter governs BioRegion-level coordination. The Tender Compact and (where the fourth template has run) the Alignment Compact govern tender-level coordination.

The three layers should be internally consistent and cross-referenced. The Charter refines the Founding Compact’s multi-BioHub protocols. The Tender Compact refines the Charter’s multi-BioHub coordination for tender-specific purposes. The Alignment Compact refines the Tender Compact’s provisions for instrument-specific readiness.

Provenance

Extracted from the four template documents in the VoG as Patron Project Prototype knowledge base. The mechanics documented here appear in each template’s own Sequencing, Cross-Platform Notes, Evidentiary Discipline, and Constraints sections. This page lifts the shared material out of the individual template pages so a reader learns the mechanics once and can then read each template page for what is specific to it.