@maestroagora/agora 1.2.2 → 1.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agents/plugins/marketplace.json +21 -21
- package/.claude-plugin/marketplace.json +15 -15
- package/.claude-plugin/plugin.json +28 -22
- package/.codex-plugin/plugin.json +46 -39
- package/LICENSE +21 -21
- package/README.md +252 -69
- package/assets/agora-orbit.svg +158 -158
- package/package.json +68 -56
- package/scripts/install.mjs +405 -400
- package/scripts/voice/check.mjs +175 -0
- package/scripts/voice/features.mjs +359 -0
- package/scripts/voice/gates.mjs +244 -0
- package/scripts/voice/ingest.mjs +226 -0
- package/scripts/voice/lexicon.mjs +162 -0
- package/scripts/voice/pipeline.mjs +186 -0
- package/scripts/voice/profile.mjs +528 -0
- package/scripts/voice-measure.mjs +369 -0
- package/skills/agora/SKILL.md +243 -17
- package/skills/agora/agents/openai.yaml +2 -2
- package/skills/agora/references/agora-case-studies.md +381 -0
- package/skills/agora/references/agora-craft.md +563 -0
- package/skills/agora/references/agora-invest.md +544 -0
- package/skills/agora/references/agora-marketing.md +716 -27
- package/skills/agora/references/agora-science.md +299 -0
- package/skills/agora/references/agora-voice.md +270 -0
|
@@ -0,0 +1,544 @@
|
|
|
1
|
+
# Agora INVEST authority
|
|
2
|
+
|
|
3
|
+
Use this reference only when the primary mode is `INVEST`: actual fundraising, investor communication, investment evaluation, diligence, or capital-allocation work. Do not load it for ordinary company profiles, marketing copy, investor-adjacent directories, or general business writing.
|
|
4
|
+
|
|
5
|
+
## Contents
|
|
6
|
+
|
|
7
|
+
1. INVEST route selection
|
|
8
|
+
2. Capital-decision intake
|
|
9
|
+
3. Investment claim ledger
|
|
10
|
+
4. Mutual fit and meeting architecture
|
|
11
|
+
5. Asset-by-asset procedures
|
|
12
|
+
6. Questions and evidence-led dialogue
|
|
13
|
+
7. Objections and unknowns
|
|
14
|
+
8. Rejection evidence ledger
|
|
15
|
+
9. Category, timing, and future narratives
|
|
16
|
+
10. Defensibility system
|
|
17
|
+
11. Product and economics
|
|
18
|
+
12. Process urgency and commitment language
|
|
19
|
+
13. Modifier and surface composition
|
|
20
|
+
14. Legal and ethical boundaries
|
|
21
|
+
15. Evaluation contract
|
|
22
|
+
16. Evidence register
|
|
23
|
+
|
|
24
|
+
The primary Agora conflict hierarchy remains controlling. This reference increases investment evidence discipline. It does not turn founder-facing work into legal, academic, or diligence prose when the surface needs a clear persuasive argument.
|
|
25
|
+
|
|
26
|
+
## INVEST route selection
|
|
27
|
+
|
|
28
|
+
Select one internal route. These routes are perspectives inside `INVEST`, not new public modes or CLI flags.
|
|
29
|
+
|
|
30
|
+
| Route | Actor and decision | Output job |
|
|
31
|
+
|---|---|---|
|
|
32
|
+
| `FUNDRAISE` | A company seeks capital | Earn the next investor decision with truthful opportunity, proof, risk, economics, and process clarity |
|
|
33
|
+
| `DILIGENCE` | An investor evaluates an opportunity | Test claims, assumptions, risks, return logic, conflicts, and missing evidence |
|
|
34
|
+
| `ALLOCATE` | A decision-maker compares uses of capital | Make alternatives, constraints, expected value, timing, and uncertainty explicit |
|
|
35
|
+
|
|
36
|
+
Choose by the decision, not by vocabulary. A founder email asking for a meeting is `FUNDRAISE`. An investment committee memo is `DILIGENCE`. A board paper comparing debt, equity, and self-funding is `ALLOCATE`. A company description in an investor directory remains `POSITION` unless it asks for or evaluates capital.
|
|
37
|
+
|
|
38
|
+
Do not let one route contaminate another:
|
|
39
|
+
|
|
40
|
+
- Founder persuasion does not control a diligence conclusion.
|
|
41
|
+
- Diligence skepticism does not force a fundraising opener into audit prose.
|
|
42
|
+
- Allocation comparison does not inherit startup-pitch conventions.
|
|
43
|
+
- A requested artifact never changes the actor whose decision it serves.
|
|
44
|
+
|
|
45
|
+
## Capital-decision intake
|
|
46
|
+
|
|
47
|
+
Require or explicitly mark missing information that would change the claim, capital decision, or legal route.
|
|
48
|
+
|
|
49
|
+
### Decision and fit
|
|
50
|
+
|
|
51
|
+
- route, audience, decision role, and next decision;
|
|
52
|
+
- investor stage, thesis, check size, geography, ownership needs, and timeline where known;
|
|
53
|
+
- company stage and financing instrument;
|
|
54
|
+
- requested asset, channel, destination, surface, and confidentiality state.
|
|
55
|
+
|
|
56
|
+
### Financing state
|
|
57
|
+
|
|
58
|
+
- amount sought;
|
|
59
|
+
- amount committed, by commitment class;
|
|
60
|
+
- current close state and decision timeline;
|
|
61
|
+
- current runway and measurement date;
|
|
62
|
+
- use of funds;
|
|
63
|
+
- operating milestones the capital is expected to change;
|
|
64
|
+
- legal, regulatory, tax, or counsel-review requirements.
|
|
65
|
+
|
|
66
|
+
### Evidence and risk
|
|
67
|
+
|
|
68
|
+
- historical metrics with source, period, denominator, and cohort;
|
|
69
|
+
- current operating state;
|
|
70
|
+
- forecasts with assumptions and sensitivity;
|
|
71
|
+
- customer, product, technical, market, economic, execution, financing, and legal risks;
|
|
72
|
+
- strongest current proof;
|
|
73
|
+
- largest unresolved uncertainty;
|
|
74
|
+
- known investor concerns;
|
|
75
|
+
- conflicts across the deck, financial model, data room, correspondence, and conversation.
|
|
76
|
+
|
|
77
|
+
Ask only when the missing information would materially change audience fit, the financing claim, the ask, the risk picture, the next action, or the legal route. Otherwise narrow the output and label the unknown.
|
|
78
|
+
|
|
79
|
+
Never invent or infer missing round terms, commitments, traction, market size, customer proof, margins, runway, investor interest, term sheets, urgency, or use-of-funds outcomes.
|
|
80
|
+
|
|
81
|
+
## Investment claim ledger
|
|
82
|
+
|
|
83
|
+
Classify every material investment claim before drafting.
|
|
84
|
+
|
|
85
|
+
| Class | Meaning | Required treatment |
|
|
86
|
+
|---|---|---|
|
|
87
|
+
| `HISTORICAL_MEASURED` | Result measured in a completed period | Preserve source, period, cohort, denominator, method, and material exclusions |
|
|
88
|
+
| `CURRENT_STATE` | Verified operating condition at a stated date | State the date and avoid converting current state into trend |
|
|
89
|
+
| `CONTRACTED_COMMITTED` | Obligation supported by an executed instrument | Name the class and relevant conditions without implying cash receipt |
|
|
90
|
+
| `CUSTOMER_REPORTED` | Customer statement rather than company measurement | Attribute it and preserve permission, scope, and typicality |
|
|
91
|
+
| `FORECAST` | Estimated future result produced by assumptions | Expose controlling assumptions, range, and sensitivity |
|
|
92
|
+
| `TARGET` | Intended future result | Do not present it as forecast, commitment, or actual result |
|
|
93
|
+
| `MODEL_ASSUMPTION` | Input used to calculate a scenario | Keep it visible enough to inspect |
|
|
94
|
+
| `INTERPRETATION` | Meaning assigned to evidence | Separate it from the evidence itself |
|
|
95
|
+
| `SCENARIO` | Conditional outcome under stated inputs | Preserve conditions and alternatives |
|
|
96
|
+
| `UNKNOWN_UNMEASURED` | Missing or unmeasured point | Say so; do not repair it rhetorically |
|
|
97
|
+
|
|
98
|
+
Never move a claim upward in certainty when compressing it.
|
|
99
|
+
|
|
100
|
+
Keep every claim coordinate exact: actor, population, sample source, period, milestone, instrument, and evidence stage. Do not substitute `buyer`, `customer`, `user`, `investor`, or `market` for one another. Do not infer independence, representativeness, diversity, or typicality from a count. Do not turn an interview sample into a population claim. Do not infer that adjacent evidence is absent because one named milestone has not occurred. Repeat the supplied milestone precisely.
|
|
101
|
+
|
|
102
|
+
Keep negative process evidence equally exact. `No term sheet`, `no stated investment amount`, and `no formal diligence` are separate facts. Do not compress them into a broader claim such as `no investment terms are in progress` unless that full process state is supplied.
|
|
103
|
+
|
|
104
|
+
### Metric separations
|
|
105
|
+
|
|
106
|
+
Keep these distinct:
|
|
107
|
+
|
|
108
|
+
- recurring revenue and one-time revenue;
|
|
109
|
+
- bookings, recognized revenue, ARR, cash collected, and pipeline;
|
|
110
|
+
- signed, contracted, verbal, indicated, and prospective commitments;
|
|
111
|
+
- gross retention and net retention;
|
|
112
|
+
- active, registered, trial, contracted, and total users or customers;
|
|
113
|
+
- gross margin, contribution margin, operating margin, and cash flow;
|
|
114
|
+
- historical performance, forecast, target, model assumption, and scenario.
|
|
115
|
+
|
|
116
|
+
Absolute and percentage changes retain baseline and period. Cohort metrics retain inclusion rules. Market size retains population, geography, period, method, price or value basis, and capture logic. Use of funds links capital to an operating milestone without guaranteeing that capital will produce it.
|
|
117
|
+
|
|
118
|
+
Perform transparent arithmetic when supplied figures make a decision-relevant ratio directly calculable. Label it as arithmetic, preserve numerator and denominator, and do not attach a causal interpretation. If implementation labor is 9,200 against first-year contract value of 18,000, about 51% is arithmetic; whether that ratio causes weak lifetime economics remains a separate question requiring retention, acquisition, delivery, and margin evidence.
|
|
119
|
+
|
|
120
|
+
## Mutual fit and meeting architecture
|
|
121
|
+
|
|
122
|
+
Treat fundraising as mutual qualification under unequal bargaining power and real legal duties. Both parties are testing fit, but that does not make their leverage, obligations, or information identical.
|
|
123
|
+
|
|
124
|
+
Fit may include:
|
|
125
|
+
|
|
126
|
+
- stage, thesis, check size, geography, ownership, reserves, and timing;
|
|
127
|
+
- market, product, technical, and economic understanding;
|
|
128
|
+
- evidence quality and risk tolerance;
|
|
129
|
+
- partner and investment-committee process;
|
|
130
|
+
- post-investment working relationship;
|
|
131
|
+
- conflicts, governance expectations, and follow-on capacity.
|
|
132
|
+
|
|
133
|
+
Write toward the next mutual decision, not toward applause.
|
|
134
|
+
|
|
135
|
+
### Brief opening
|
|
136
|
+
|
|
137
|
+
Establish only what the next exchange needs:
|
|
138
|
+
|
|
139
|
+
1. What the company does in reader-owned language.
|
|
140
|
+
2. The strongest current proof.
|
|
141
|
+
3. The verified opportunity, transition, or reason timing matters.
|
|
142
|
+
4. The capital decision or next step when the surface requires it.
|
|
143
|
+
|
|
144
|
+
Once the listener can identify company, evidence, opportunity, and next decision, stop adding setup. Invite the live question or continue into the mechanism the surface requires. No fixed duration, speaking ratio, or equal-part formula applies.
|
|
145
|
+
|
|
146
|
+
Complex, unfamiliar, regulated, or scientific opportunities may need more orientation before questions become useful. Safety-critical or legally required information is never delayed to create suspense.
|
|
147
|
+
|
|
148
|
+
When the problem evidence comes from interviews, pilots, or one named cohort, attribute that evidence before stating the problem as a broader condition. The opening may make the evidence consequential, but it may not enlarge the observed population.
|
|
149
|
+
|
|
150
|
+
### Evidence-led dialogue
|
|
151
|
+
|
|
152
|
+
State the intended conclusion. Supply the facts that support it. Leave room for scrutiny. Do not make investors infer a material fact, risk, conflict, ask, or use of funds as a persuasion tactic.
|
|
153
|
+
|
|
154
|
+
Questions are useful when they expose the live decision criteria. They are not useful when they merely force participation, hide weak preparation, or pressure the investor toward a predetermined answer.
|
|
155
|
+
|
|
156
|
+
## Asset-by-asset procedures
|
|
157
|
+
|
|
158
|
+
Fundraising uses related assets with different jobs. There is no universal sequence.
|
|
159
|
+
|
|
160
|
+
### Introduction request
|
|
161
|
+
|
|
162
|
+
Give the mutual contact enough accurate material to decide whether to introduce:
|
|
163
|
+
|
|
164
|
+
- why the recipient is relevant;
|
|
165
|
+
- company in one clear line;
|
|
166
|
+
- one decision-relevant proof point;
|
|
167
|
+
- the specific introduction requested;
|
|
168
|
+
- a forwardable note that does not overstate the relationship.
|
|
169
|
+
|
|
170
|
+
Do not make the contact endorse claims they cannot verify.
|
|
171
|
+
|
|
172
|
+
### Direct outreach
|
|
173
|
+
|
|
174
|
+
Direct outreach is valid when it is truthful, specific, appropriately targeted, and low-friction. State fit, company, one proof point, why this recipient is relevant, and one concrete next action. Do not claim a universal failure rate for direct outreach or a universal advantage for warm introductions.
|
|
175
|
+
|
|
176
|
+
### Short company brief
|
|
177
|
+
|
|
178
|
+
Orient the reader, establish proof and opportunity, state the ask when needed, show the main risk or unknown, and provide a destination for the next evidence layer. It is not a compressed deck if the recipient needs a different decision path.
|
|
179
|
+
|
|
180
|
+
In a one-paragraph brief, keep measured or reported result, evidentiary boundary, interpretation, and capital use as distinct sentence jobs. Do not stack claim classification, limitation, and opportunity interpretation into one long sentence merely to keep the asset to one paragraph.
|
|
181
|
+
|
|
182
|
+
Do not join an evidence limitation to a positive interpretation with `but`. That construction discounts the boundary. State the boundary in its own sentence, then make only the separate interpretation the evidence supports.
|
|
183
|
+
|
|
184
|
+
State use of capital as the concrete operating action it funds. Do not replace `add reviewer-system integrations` with abstractions such as `capital-relevant operating objective`, `integration wedge`, or `deployment thesis`.
|
|
185
|
+
|
|
186
|
+
For a founder-facing fundraising brief, connect present evidence to the proposed use of capital, the operating change or uncertainty the capital is meant to test, and the next investor decision. Do not return a metric inventory. A stated use of funds does not by itself prove that the named area is the current constraint.
|
|
187
|
+
|
|
188
|
+
### Meeting opening
|
|
189
|
+
|
|
190
|
+
Use the brief-opening procedure. Do not recite every slide. Do not withhold basic orientation to manufacture curiosity.
|
|
191
|
+
|
|
192
|
+
### Demo framing
|
|
193
|
+
|
|
194
|
+
Put the investor in the relevant customer or system state. Show the mechanism, evidence, and limit. Connect the demo to product, market, economic, or execution evidence. Avoid feature tours with no capital-decision argument.
|
|
195
|
+
|
|
196
|
+
### Deck
|
|
197
|
+
|
|
198
|
+
Build a standalone argument that can survive internal forwarding. The deck must not depend on founder narration to repair a material omission. Stage, investor context, medium, and available evidence control depth and order.
|
|
199
|
+
|
|
200
|
+
The deck should let a reader locate:
|
|
201
|
+
|
|
202
|
+
- company and customer;
|
|
203
|
+
- problem or transition;
|
|
204
|
+
- product and mechanism;
|
|
205
|
+
- evidence and traction at the supplied level;
|
|
206
|
+
- market and capture logic;
|
|
207
|
+
- business and economic model;
|
|
208
|
+
- competition and category;
|
|
209
|
+
- team evidence;
|
|
210
|
+
- material risks and unknowns at the depth the stage requires;
|
|
211
|
+
- financing ask, use of funds, and milestones.
|
|
212
|
+
|
|
213
|
+
These are decision elements, not a fixed slide count or sequence. If an investor requests the deck before a meeting, provide the right standalone deck unless confidentiality, legal, or strategic constraints justify another response.
|
|
214
|
+
|
|
215
|
+
### Follow-up
|
|
216
|
+
|
|
217
|
+
Reflect the actual questions. Answer with evidence. State unresolved items, owners, and dates. Name the next decision. Do not replace a specific discussion with a generic recap.
|
|
218
|
+
|
|
219
|
+
Return a complete channel-native artifact. For email, include a useful subject line, greeting, body, and sign-off unless the user requests body copy only or supplies a wrapper that already contains them. These framing elements may orient the recipient and action; they may not add urgency, relationship, commitment, or process claims.
|
|
220
|
+
|
|
221
|
+
Close on the actual next decision. Sending a deck, update, or answer does not by itself tell the recipient what to decide. When the brief supplies the process, name the next decision such as partner review, confirmation of fit, scheduling a discussion, opening diligence, or declining. An offer to send more material is not a substitute for that decision.
|
|
222
|
+
|
|
223
|
+
When no real decision deadline is supplied, request the next decision without a reply-by date. Do not invent Friday, end-of-week, allocation, or closing pressure after correctly stating that no deadline exists.
|
|
224
|
+
|
|
225
|
+
When the next decision is whether to schedule another meeting, make the scheduling request operational: ask for confirmation, relevant participants, and workable time options. Ask for topics or evidence only when that information changes preparation. Do not make the recipient invent the whole next step.
|
|
226
|
+
|
|
227
|
+
### Diligence answer
|
|
228
|
+
|
|
229
|
+
Give the direct answer first. Classify fact, assumption, forecast, target, scenario, and unknown. Name the source and relevant date. Record conflicts across artifacts rather than silently harmonizing them.
|
|
230
|
+
|
|
231
|
+
### Partner or investment-committee brief
|
|
232
|
+
|
|
233
|
+
Write for internal forwarding. Make the thesis, disconfirming evidence, material risk, return logic, open questions, and required next decision locatable without founder narration.
|
|
234
|
+
|
|
235
|
+
### Data-room index
|
|
236
|
+
|
|
237
|
+
Organize by the evaluator's decision and verification needs. Identify owner, period, version, confidentiality, and known gap. A complete-looking index must not imply that missing evidence exists.
|
|
238
|
+
|
|
239
|
+
### Progress update
|
|
240
|
+
|
|
241
|
+
State what changed, when, and how it was measured. Separate current facts from outlook. Connect the update to the prior question or milestone. Do not manufacture momentum from activity volume.
|
|
242
|
+
|
|
243
|
+
## Questions and evidence-led dialogue
|
|
244
|
+
|
|
245
|
+
Useful questions include:
|
|
246
|
+
|
|
247
|
+
- Which part of the opportunity fits or conflicts with the fund's thesis?
|
|
248
|
+
- What evidence would be required for the next decision?
|
|
249
|
+
- Which risk is currently most decision-relevant?
|
|
250
|
+
- Who else participates in the decision?
|
|
251
|
+
- What must the recipient explain internally?
|
|
252
|
+
- Which company assumption appears weakest?
|
|
253
|
+
- What would make the opportunity clearly wrong for this investor?
|
|
254
|
+
- Which claim requires a source, cohort, or sensitivity that is not yet supplied?
|
|
255
|
+
|
|
256
|
+
Use answers to select evidence and follow-up. Do not use questions to manipulate agreement, delay a direct answer, or pressure the other party into defending the company for you.
|
|
257
|
+
|
|
258
|
+
Ask no question whose answer is already documented unless the purpose is to resolve a conflict or test whether the documented point remains current.
|
|
259
|
+
|
|
260
|
+
## Objections and unknowns
|
|
261
|
+
|
|
262
|
+
Treat an objection as a decision signal and possible evidence request, not as an enemy to defeat.
|
|
263
|
+
|
|
264
|
+
Use this sequence when it fits the surface:
|
|
265
|
+
|
|
266
|
+
1. Restate the concern accurately.
|
|
267
|
+
2. Accept any valid premise.
|
|
268
|
+
3. Classify the disputed point as fact, forecast, assumption, unknown, interpretation, or preference.
|
|
269
|
+
4. Give the strongest relevant evidence.
|
|
270
|
+
5. State the remaining limit or weakness.
|
|
271
|
+
6. Define the next verification step, owner, and date when available.
|
|
272
|
+
|
|
273
|
+
Do not mechanically agree and redirect. Do not turn every weakness into a strength. A valid weakness remains a weakness until evidence changes it. If a question requires a qualified legal, financial, tax, safety, or technical owner, route it rather than improvising an answer.
|
|
274
|
+
|
|
275
|
+
When no answer exists, say what is unknown, why it matters, what evidence would resolve it, and whether the decision can proceed without it.
|
|
276
|
+
|
|
277
|
+
A count of people raising the same objection does not establish that they are independent. One passed review establishes that one review passed, not that a general security posture, procurement path, or deployment process clears. Define the next test across the exact stages the decision needs, such as stated willingness, entry into review, approval, deployment, renewal, and measured timing. Do not collapse an earlier stage into a later one.
|
|
278
|
+
|
|
279
|
+
## Rejection evidence ledger
|
|
280
|
+
|
|
281
|
+
Use rejection feedback as evidence to investigate.
|
|
282
|
+
|
|
283
|
+
Record:
|
|
284
|
+
|
|
285
|
+
- investor fit and stated reason;
|
|
286
|
+
- stage of process;
|
|
287
|
+
- exact concern in paraphrase unless an approved exact record is required;
|
|
288
|
+
- whether the concern is factual, interpretive, strategic, process-based, or preference-based;
|
|
289
|
+
- evidence already supplied;
|
|
290
|
+
- conflicts with other feedback or observed customer evidence;
|
|
291
|
+
- action taken;
|
|
292
|
+
- result after the change;
|
|
293
|
+
- whether the source population is relevant to the decision being changed.
|
|
294
|
+
|
|
295
|
+
Repeated feedback is not truth by repetition. Correlated investors may repeat the same unsupported assumption. No fixed count converts opinion into market fact. Validate against customers, company data, market evidence, or the relevant decision population.
|
|
296
|
+
|
|
297
|
+
Do not optimize every asset after every rejection. Change an argument when the evidence, target fit, or repeated decision failure gives a reason that survives contradiction review.
|
|
298
|
+
|
|
299
|
+
## Category, timing, and future narratives
|
|
300
|
+
|
|
301
|
+
A supported investment narrative may explain:
|
|
302
|
+
|
|
303
|
+
1. The current system or category.
|
|
304
|
+
2. The observable transition.
|
|
305
|
+
3. The decision the transition changes.
|
|
306
|
+
4. The attributes a successful response requires.
|
|
307
|
+
5. The company's evidence against those attributes.
|
|
308
|
+
6. The uncertainties that remain.
|
|
309
|
+
|
|
310
|
+
Use a familiar category when it helps comparison. Create or name a new category only when the supplied facts show a distinct decision frame that existing language cannot carry without material distortion.
|
|
311
|
+
|
|
312
|
+
Never:
|
|
313
|
+
|
|
314
|
+
- create a category merely to avoid competitors;
|
|
315
|
+
- use zero search results as proof that a category is valid;
|
|
316
|
+
- claim that new categories outperform familiar ones as a universal rule;
|
|
317
|
+
- describe a future as inevitable without qualifying evidence;
|
|
318
|
+
- assign certainty to timing that the evidence cannot support;
|
|
319
|
+
- convert a broad technology trend into company-specific demand.
|
|
320
|
+
|
|
321
|
+
Timing claims require an observable trigger, relevant scope, and a reason it changes this capital decision now. Trend language is a claim.
|
|
322
|
+
|
|
323
|
+
A horizon named in rejected source copy is not a supported forecast. If the supplied surveys or data do not forecast through that year, do not claim broader uptake through the horizon. Build the timing case from the current observed transition and the company's current evidence.
|
|
324
|
+
|
|
325
|
+
Keep the trend category exact. Evidence about `computer-vision inspection` does not establish adoption of `autonomous quality control`. A paid pilot supports willingness to pay for that pilot, not renewal strength, repeatable deployment, market share, or category ownership.
|
|
326
|
+
|
|
327
|
+
When asked for the strongest defensible future case, finish the argument conditionally: supplied trend in its actual population, current company evidence, next proof required, and the position that could become credible if that proof arrives. Do not stop at a risk ledger, and do not recover rhetorical force by broadening the trend population.
|
|
328
|
+
|
|
329
|
+
## Defensibility system
|
|
330
|
+
|
|
331
|
+
Assess defensibility as interacting mechanisms, not one adjective.
|
|
332
|
+
|
|
333
|
+
Possible layers include:
|
|
334
|
+
|
|
335
|
+
- product or technical capability;
|
|
336
|
+
- data, learning, workflow, or operating method;
|
|
337
|
+
- business and economic model;
|
|
338
|
+
- distribution and go-to-market access;
|
|
339
|
+
- switching, network, regulatory, scale, or integration effects when verified;
|
|
340
|
+
- team-specific execution evidence.
|
|
341
|
+
|
|
342
|
+
For each layer, record:
|
|
343
|
+
|
|
344
|
+
- current evidence;
|
|
345
|
+
- maturity state;
|
|
346
|
+
- replication path and cost;
|
|
347
|
+
- dependency;
|
|
348
|
+
- failure condition;
|
|
349
|
+
- whether the effect strengthens, weakens, or remains unknown as the company scales.
|
|
350
|
+
|
|
351
|
+
Several layers do not automatically create a moat. Integration complexity can be a liability. Early-stage defensibility often remains a hypothesis. Use the narrowest accurate language.
|
|
352
|
+
|
|
353
|
+
## Product and economics
|
|
354
|
+
|
|
355
|
+
The material must explain both sides of the company.
|
|
356
|
+
|
|
357
|
+
### Product
|
|
358
|
+
|
|
359
|
+
- what is being built;
|
|
360
|
+
- for whom;
|
|
361
|
+
- which situation or decision it changes;
|
|
362
|
+
- how the mechanism works;
|
|
363
|
+
- what evidence supports it;
|
|
364
|
+
- what it cannot yet do;
|
|
365
|
+
- what must be true to scale it.
|
|
366
|
+
|
|
367
|
+
### Economics
|
|
368
|
+
|
|
369
|
+
- how value is captured;
|
|
370
|
+
- price, contract, and revenue basis where supplied;
|
|
371
|
+
- which costs scale with usage, sales, support, infrastructure, regulation, or delivery;
|
|
372
|
+
- historical unit economics at their actual maturity level;
|
|
373
|
+
- forecast assumptions and sensitivities;
|
|
374
|
+
- capital requirements;
|
|
375
|
+
- what the proposed financing changes;
|
|
376
|
+
- downside and alternative plans.
|
|
377
|
+
|
|
378
|
+
Product strength does not repair unsupported unit economics. Economic optimism does not repair an undifferentiated product. A forecast is not a historical result. A target is not a forecast. A plan is not a commitment.
|
|
379
|
+
|
|
380
|
+
Keep operating facts separate unless evidence links them. A use of funds to reduce installation labor does not establish that installation labor caused the current gross margin, and a gross-margin figure does not identify its cost driver. Present the margin, labor plan, and verification question separately.
|
|
381
|
+
|
|
382
|
+
### Use of funds
|
|
383
|
+
|
|
384
|
+
Connect each material use to:
|
|
385
|
+
|
|
386
|
+
- amount or range;
|
|
387
|
+
- operating action;
|
|
388
|
+
- milestone;
|
|
389
|
+
- expected evidence produced;
|
|
390
|
+
- decision date;
|
|
391
|
+
- dependency and downside response.
|
|
392
|
+
|
|
393
|
+
Use `is intended to`, `is expected to`, or `would fund` according to the evidence. Do not state that capital guarantees the milestone.
|
|
394
|
+
|
|
395
|
+
### Allocation comparisons
|
|
396
|
+
|
|
397
|
+
Compare the named alternatives over the same period, operating base, and decision criteria. Separate supplied facts from arithmetic, assumptions, scenarios, and unknowns. Do not calculate expected value or rank options by probability when no probability model is supplied.
|
|
398
|
+
|
|
399
|
+
Do not invent a minimum-runway threshold, financing trigger, hurdle rate, portfolio weight, stop-loss, decision date, or other numeric policy. Use a supplied policy when authorized. If the task explicitly asks for a new governance rule, label the number as a proposed governance default and expose the reason, owner, review point, and failure condition. Otherwise state the decision condition qualitatively.
|
|
400
|
+
|
|
401
|
+
When financing terms, operating sensitivities, or material outcome evidence are missing, narrow the conclusion. The supported decision may be to preserve an available option, obtain the missing evidence, or defer authorization. Missing comparison inputs do not license a precise recommendation.
|
|
402
|
+
|
|
403
|
+
## Process urgency and commitment language
|
|
404
|
+
|
|
405
|
+
Urgency must come from a current supplied process fact.
|
|
406
|
+
|
|
407
|
+
Potentially usable facts include:
|
|
408
|
+
|
|
409
|
+
- an actual financing deadline;
|
|
410
|
+
- verified runway and measurement date;
|
|
411
|
+
- a supplied allocation state;
|
|
412
|
+
- a current decision window;
|
|
413
|
+
- executed or clearly classified commitments;
|
|
414
|
+
- active diligence at its real stage;
|
|
415
|
+
- an external regulatory, contractual, or operating deadline.
|
|
416
|
+
|
|
417
|
+
Keep commitment classes exact:
|
|
418
|
+
|
|
419
|
+
| State | Allowed treatment |
|
|
420
|
+
|---|---|
|
|
421
|
+
| Executed and binding | State the relevant executed commitment and conditions |
|
|
422
|
+
| Signed but conditional | State the condition |
|
|
423
|
+
| Verbal indication | Attribute it as non-binding verbal interest |
|
|
424
|
+
| Active discussion | State the discussion stage without implying commitment |
|
|
425
|
+
| Prospective target | State it as a target, not interest |
|
|
426
|
+
| Unknown | Do not imply demand |
|
|
427
|
+
|
|
428
|
+
Never imply a term sheet, lead, commitment, advanced diligence, scarcity, competing demand, or closing pressure that does not exist. Do not behave as if a term sheet exists to manufacture social proof. Do not withhold basic information as a reward for engagement.
|
|
429
|
+
|
|
430
|
+
A true fact can still mislead through omitted context. Review the net impression created by timing, quantity, investor names, and commitment language.
|
|
431
|
+
|
|
432
|
+
Lock process-state language to the supplied class in every derivative phrase. A `scheduled closing` remains scheduled; a `target close` remains a target; a `current allocation` remains current only for its supplied date. Do not shorten these to `the close`, `ahead of the close`, `closing now`, or another phrase that turns a plan into a settled event.
|
|
433
|
+
|
|
434
|
+
## Modifier and surface composition
|
|
435
|
+
|
|
436
|
+
### `INVEST + SCIENCE`
|
|
437
|
+
|
|
438
|
+
Load both references. Scientific and technical uncertainty, current authoritative verification, calibrated causality, and exact terminology override investment vision language. Explain the mechanism clearly enough for the decision role. Do not convert technical possibility into product readiness, regulatory clearance, customer demand, or commercial scale.
|
|
439
|
+
|
|
440
|
+
Connect the financing to the exact next validation question: what effect, condition, scale, replication, lifetime, safety, cost, or customer evidence the capital is meant to test. `Validation financing` alone is not a decision-ready use of funds.
|
|
441
|
+
|
|
442
|
+
### `INVEST + CASE_STUDY`
|
|
443
|
+
|
|
444
|
+
Load both references. A customer case remains evidence about its stated subject, period, intervention, and measurement. It is not proof of general market performance, typicality, causal product impact, or future company results unless the evidence separately supports those claims.
|
|
445
|
+
|
|
446
|
+
### `INVEST + VOICE`
|
|
447
|
+
|
|
448
|
+
Financial evidence, forecast classification, required disclosure, quote fidelity, and uncertainty override habitual certainty, bravado, compression, or informality in the profile.
|
|
449
|
+
|
|
450
|
+
When a confident profile uses `will require` for a necessary condition, name the concrete action each dependency must complete. Write `renewals to close` and `contracts to sign`, not a compressed noun list that leaves completion implicit. State the condition directly. Do not preface it with `one thing is certain` or another certainty claim merely to imitate the profile.
|
|
451
|
+
|
|
452
|
+
Preserve the exact actor, present status, and dependency while applying rhythm. `Management targets` cannot become `we will achieve`. Unsigned renewals remain unsigned and uncommitted prospects remain uncommitted. A confident profile may use `will require` to state a necessary condition because the certainty belongs to the dependency, not the forecast outcome. Do not turn a recommended next research or financing step into `we will` unless an approved plan is supplied.
|
|
453
|
+
|
|
454
|
+
### `INVEST + GEO/AEO`
|
|
455
|
+
|
|
456
|
+
Apply written GEO/AEO only to indexable public assets. Public fundraising pages require current legal-route and page-level claim review. Private decks, meetings, diligence responses, and data-room assets do not inherit search formatting.
|
|
457
|
+
|
|
458
|
+
### `FUNDRAISE + SELL`
|
|
459
|
+
|
|
460
|
+
Do not combine primary modes. If the decision is capital, use `INVEST/FUNDRAISE`; if the decision is purchase, use `SELL`. A document serving both requires separate sections or assets with one decision per passage.
|
|
461
|
+
|
|
462
|
+
## Legal and ethical boundaries
|
|
463
|
+
|
|
464
|
+
Capital-raising communication can create legal obligations. Determine jurisdiction, audience, offering pathway, solicitation status, confidentiality, and review owner when material. Use current authoritative sources and qualified counsel. Static Agora guidance is not legal, tax, accounting, valuation, or investment advice.
|
|
465
|
+
|
|
466
|
+
Truth and material omission review precedes persuasive optimization.
|
|
467
|
+
|
|
468
|
+
Never invent or distort:
|
|
469
|
+
|
|
470
|
+
- securities terms;
|
|
471
|
+
- investor eligibility;
|
|
472
|
+
- commitments or demand;
|
|
473
|
+
- cap-table state;
|
|
474
|
+
- historical financials;
|
|
475
|
+
- forecasts or assumptions;
|
|
476
|
+
- valuation support;
|
|
477
|
+
- customer or partner relationships;
|
|
478
|
+
- regulatory status;
|
|
479
|
+
- risks, conflicts, or use of funds.
|
|
480
|
+
|
|
481
|
+
Do not provide a personalized recommendation to buy or sell a security unless the task, authority, and applicable professional requirements support it. Diligence outputs identify evidence and uncertainty; they do not manufacture investment certainty.
|
|
482
|
+
|
|
483
|
+
Confidential or personal information remains at the supplied authorization level. Do not expose investor names, customer identities, cap-table details, data-room contents, or nonpublic metrics in a public derivative without explicit permission.
|
|
484
|
+
|
|
485
|
+
## Evaluation contract
|
|
486
|
+
|
|
487
|
+
### Hard gates
|
|
488
|
+
|
|
489
|
+
Reject any output that:
|
|
490
|
+
|
|
491
|
+
- invents traction, commitments, term sheets, urgency, investor demand, market size, economics, or use-of-funds outcomes;
|
|
492
|
+
- presents a historical result as forecast certainty;
|
|
493
|
+
- presents a target, assumption, scenario, pipeline item, or verbal indication as actual or committed;
|
|
494
|
+
- omits a supplied material risk, conflict, qualification, or use of funds;
|
|
495
|
+
- uses a misleading category, inevitability, scarcity, or timing claim;
|
|
496
|
+
- hides a valid weakness through reframing;
|
|
497
|
+
- lets founder persuasion contaminate diligence or allocation;
|
|
498
|
+
- invents a numeric decision threshold, probability, expected value, or financing trigger;
|
|
499
|
+
- changes a supplied actor, population, sample property, evidence stage, or milestone into a broader claim;
|
|
500
|
+
- invents a reply date where no process deadline exists;
|
|
501
|
+
- implies that a deck, meeting format, warm introduction, talk ratio, or fixed duration causes funding;
|
|
502
|
+
- exposes private or confidential material;
|
|
503
|
+
- produces legal or investment advice beyond the supplied authority.
|
|
504
|
+
|
|
505
|
+
### Quality dimensions
|
|
506
|
+
|
|
507
|
+
Evaluate:
|
|
508
|
+
|
|
509
|
+
- decision and route fit;
|
|
510
|
+
- company and opportunity clarity;
|
|
511
|
+
- evidence traceability;
|
|
512
|
+
- claim-class fidelity;
|
|
513
|
+
- risk visibility;
|
|
514
|
+
- forecast and assumption transparency;
|
|
515
|
+
- product and economic coherence;
|
|
516
|
+
- ask and use-of-funds clarity;
|
|
517
|
+
- objection integrity;
|
|
518
|
+
- internal-forwarding strength;
|
|
519
|
+
- next-decision clarity;
|
|
520
|
+
- legal-route awareness;
|
|
521
|
+
- first-read comprehension and natural channel fit.
|
|
522
|
+
|
|
523
|
+
### Hostile readers
|
|
524
|
+
|
|
525
|
+
- Founder: can explain company, proof, opportunity, ask, economics, and risks without inventing certainty.
|
|
526
|
+
- Investor: can identify what is historical, current, committed, forecast, targeted, assumed, conditional, and unknown.
|
|
527
|
+
- Counsel: can locate each offering claim and material omission for current review.
|
|
528
|
+
- Partner: can forward the argument without founder narration repairing it.
|
|
529
|
+
- Skeptic: can find a direct response to the strongest objection and the remaining weakness.
|
|
530
|
+
- Allocator: can compare alternatives, constraints, expected value, timing, and uncertainty.
|
|
531
|
+
|
|
532
|
+
## Evidence register
|
|
533
|
+
|
|
534
|
+
| Rule family | Grade | Evidence and boundary |
|
|
535
|
+
|---|---|---|
|
|
536
|
+
| Securities-law route and current review | A | [SEC Capital-Raising Building Blocks](https://www.sec.gov/resources-small-businesses/capital-raising-building-blocks) identifies offering pathways, solicitation, compliance, and investor topics. It is staff guidance, not a substitute for applicable law or counsel. |
|
|
537
|
+
| Venture decision variation and sourcing | B | [How Do Venture Capitalists Make Decisions?](https://www.nber.org/papers/w22587) surveys institutional VCs and reports variation by stage, industry, geography, and practice. It does not establish universal founder tactics or current conversion rates. |
|
|
538
|
+
| Current deck attention and section behavior | C | [DocSend seed-deck research](https://www.docsend.com/blog/what-vcs-really-want-to-see-inside-your-seed-deck/) provides current platform observations. Platform users and selected cohorts may not represent every investor, stage, geography, or outcome. Average review behavior is not a fixed drafting law. |
|
|
539
|
+
| Mutual qualification and brief-opening procedure | HOUSE/PI | Useful workflow synthesized from bounded practitioner material. No causal funding effect, fixed duration, or talk ratio is claimed. |
|
|
540
|
+
| Asset routing, objection handling, and rejection ledger | HOUSE | Governance procedures. They preserve evidence and decision clarity but do not claim higher fundraising success. |
|
|
541
|
+
| Claim ledger, urgency, and commitment classes | HOUSE plus existing truth doctrine | Internal controls that prevent unsupported promotion. Current legal review still governs an actual offering. |
|
|
542
|
+
| Category and defensibility procedures | HOUSE/PI | Decision frameworks with explicit failure conditions. They do not prove category creation, defensibility, or investment returns. |
|
|
543
|
+
|
|
544
|
+
Do not promote views, likes, anecdotes, fundraising outcomes, or practitioner confidence into causal evidence. Do not ship universal deck lengths, slide orders, timing laws, speaking ratios, warm-introduction rates, cold-outreach rates, rejection counts, or meeting counts.
|