polymath-society 0.2.4
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/LICENSE +52 -0
- package/README.md +311 -0
- package/dist/DATA-MAP.md +109 -0
- package/dist/cli.js +24136 -0
- package/dist/engine/closing-rubric.md +50 -0
- package/dist/engine/exp-allfacets.js +16832 -0
- package/dist/engine/exp-person.js +16922 -0
- package/dist/engine/exp-pipeline.js +16700 -0
- package/dist/engine/feel-seen-rubric.md +192 -0
- package/dist/engine/ingest-export.js +1423 -0
- package/dist/engine/peak-demos.js +16752 -0
- package/dist/engine/person-dimension-summary.js +16744 -0
- package/dist/engine/person-facet-lines.js +16784 -0
- package/dist/engine/person-headline.js +16733 -0
- package/dist/engine/person-report.js +16845 -0
- package/dist/engine/person-self-image.js +16689 -0
- package/dist/engine/public-report-guidelines.md +80 -0
- package/dist/engine/public-report.js +17284 -0
- package/dist/engine/run-analysis.js +16035 -0
- package/dist/engine/run-tagger.js +16092 -0
- package/dist/engine/top-companies.md +41 -0
- package/dist/engine/writing-well.md +56 -0
- package/dist/index.js +22021 -0
- package/dist/pipeline/TECHNIQUES.md +406 -0
- package/dist/pipeline/WRITING.md +48 -0
- package/dist/pipeline/coding-agglomerate.js +15876 -0
- package/dist/pipeline/coding-aggregate.js +440 -0
- package/dist/pipeline/coding-build.js +1168 -0
- package/dist/pipeline/coding-coaching.js +16893 -0
- package/dist/pipeline/coding-day-digest.js +15869 -0
- package/dist/pipeline/coding-delegation.js +16292 -0
- package/dist/pipeline/coding-expertise.js +15925 -0
- package/dist/pipeline/coding-flow.js +313 -0
- package/dist/pipeline/coding-frontier-detail.js +15878 -0
- package/dist/pipeline/coding-frontier.js +51 -0
- package/dist/pipeline/coding-gap-dist.js +293 -0
- package/dist/pipeline/coding-gap.js +17108 -0
- package/dist/pipeline/coding-grade.js +16195 -0
- package/dist/pipeline/coding-nutshell.js +15725 -0
- package/dist/pipeline/coding-projects.js +104 -0
- package/dist/pipeline/coding-walkthrough.js +15947 -0
- package/dist/web/app.js +12024 -0
- package/dist/web/index.html +1 -0
- package/dist/web/styles.css +1 -0
- package/package.json +61 -0
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# TOP DESTINATIONS RUBRIC — naming real, desirable places in the trajectory line
|
|
2
|
+
|
|
3
|
+
When the report's close names where someone of this caliber could go, name **actual,
|
|
4
|
+
currently-desirable places**, matched to THEIR field and level. "A serious company
|
|
5
|
+
with serious backing" is vague and weak. "You are the caliber of Anthropic or
|
|
6
|
+
OpenAI, and you would be a standout founder" lands, because it is concrete.
|
|
7
|
+
|
|
8
|
+
## Rules
|
|
9
|
+
- Name **1–3 real places**, matched to the person's actual domain (from their profile).
|
|
10
|
+
- Only name what their evidence genuinely supports. Never inflate. A 7 is "great at
|
|
11
|
+
a top company"; a 9–11 is "the caliber of the very best, or a fundable founder."
|
|
12
|
+
- These are a **proxy for the height they could reach**, not a job suggestion. After
|
|
13
|
+
naming them, point PAST them to the larger, civilization-scale thing.
|
|
14
|
+
- Founder path is a first-class destination, not a fallback.
|
|
15
|
+
- Keep it current. The list below is the desirable set "lately" (2025–2026); prefer
|
|
16
|
+
these over dated names (Goldman, McKinsey, generic FAANG) unless they truly fit.
|
|
17
|
+
|
|
18
|
+
## The set, by domain
|
|
19
|
+
- **Frontier AI / research labs:** Anthropic, OpenAI, Google DeepMind. (also: xAI,
|
|
20
|
+
Thinking Machines, Safe Superintelligence, Mistral, Meta Superintelligence Labs)
|
|
21
|
+
- **AI product / applied (hot scaleups):** Cursor (Anysphere), Perplexity, Scale AI,
|
|
22
|
+
OpenAI/Anthropic product, Figma, Ramp, Stripe, Databricks.
|
|
23
|
+
- **Quant trading / HFT:** Jane Street, Citadel / Citadel Securities, Hudson River
|
|
24
|
+
Trading, Two Sigma, Jump Trading, D. E. Shaw, Optiver.
|
|
25
|
+
- **Elite general engineering:** Google, Nvidia, Meta, Apple, Stripe.
|
|
26
|
+
- **Founder:** building their own company, backed by Y Combinator / a16z / Sequoia /
|
|
27
|
+
Founders Fund. For a generational profile, this is often the truest fit.
|
|
28
|
+
- **Research / academia:** a top PhD or lab (MIT, Stanford, Berkeley, CMU), or
|
|
29
|
+
research at DeepMind / FAIR.
|
|
30
|
+
- **Design / craft:** the design-led ones (Figma, Linear, Apple, Vercel).
|
|
31
|
+
|
|
32
|
+
## Caliber → what to name
|
|
33
|
+
- **Generational (their domain score ~10–11):** the very top labs (Anthropic,
|
|
34
|
+
OpenAI, DeepMind) AND a fundable founder. Then the civilization-scale future.
|
|
35
|
+
- **Exceptional (8–9):** a standout at those, or a strong founder.
|
|
36
|
+
- **Strong (7):** great at a top company in their field.
|
|
37
|
+
|
|
38
|
+
## Example (an AI-leaning founder, generational reasoning)
|
|
39
|
+
> "You are the caliber of the people Anthropic and OpenAI are built around, and you
|
|
40
|
+
> would be a standout founder with real backing. But the thing actually visible in
|
|
41
|
+
> you is bigger than any single seat: ..." (then the civilization-scale line)
|
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
# WRITING WELL — how to write so it doesn't read like AI
|
|
2
|
+
|
|
3
|
+
This is about how the copy READS. It is SEPARATE from the feel-seen rubric (which is
|
|
4
|
+
about what to recognize and say). These are the style rules. Re-read your output
|
|
5
|
+
against them before returning it.
|
|
6
|
+
|
|
7
|
+
1. **No em dashes (—).** The single clearest tell a machine wrote it. Use a period,
|
|
8
|
+
a comma, or a colon; rewrite the sentence if you have to. Target zero; at most one
|
|
9
|
+
in a whole piece, and only if nothing else works. Same for the spaced hyphen used
|
|
10
|
+
as a dash. Just start a new sentence.
|
|
11
|
+
|
|
12
|
+
2. **Never invent.** Do not state an event, action, or outcome as fact unless it is
|
|
13
|
+
literally in the evidence you were given. Do not infer that something happened from
|
|
14
|
+
a feeling or a fragment ("he called her family", "it worked out"). When unsure it
|
|
15
|
+
happened, leave it out. A true smaller specific beats an invented bigger one.
|
|
16
|
+
|
|
17
|
+
3. **No jargon, no bare proper nouns.** Plain words a smart friend with no background
|
|
18
|
+
understands. If you must use a term, unpack it in the same breath. (Naming a famous
|
|
19
|
+
person for stature is fine; bare domain jargon is not.)
|
|
20
|
+
|
|
21
|
+
4. **No fluff or throat-clearing.** Every sentence carries real, specific content.
|
|
22
|
+
Cut "here's the thing", "the truth is", "what's remarkable is". If a clause can be
|
|
23
|
+
deleted with no loss of meaning, delete it.
|
|
24
|
+
|
|
25
|
+
5. **Plain declarative sentences.** Don't stack clause on clause. Short and clear
|
|
26
|
+
beats ornate. Never ship a half-formed garble; if a sentence isn't clean and
|
|
27
|
+
grammatical, rewrite it.
|
|
28
|
+
|
|
29
|
+
6. **Avoid the stock AI cadences.** Don't lean on "it's not X, it's Y", "isn't just
|
|
30
|
+
X, it's Y", rule-of-three rhythms, "the kind of X that Y", or a dramatic one-line
|
|
31
|
+
paragraph for effect. Once is fine; as a pattern it reads as slop.
|
|
32
|
+
|
|
33
|
+
7. **Don't over-emphasize.** Bold or italic only where it genuinely helps.
|
|
34
|
+
|
|
35
|
+
8. **Reach for the concrete.** Where it fits, back a claim with a real, specific
|
|
36
|
+
instance of their behavior (a move, a moment, a line they wrote) instead of a bare
|
|
37
|
+
adjective. A claim with an example behind it lands harder than a floating one.
|
|
38
|
+
This is a preference, not a hard gate: don't force an example where the format is a
|
|
39
|
+
single tight line and it won't fit, and never pad with a weak or invented one.
|
|
40
|
+
|
|
41
|
+
9. **Prefer real names by tier.** When you name someone's caliber or where they could
|
|
42
|
+
go, prefer actual, currently-desirable places matched to their field and level
|
|
43
|
+
(Anthropic, OpenAI, Google DeepMind for frontier AI; Jane Street, Citadel for
|
|
44
|
+
quant; Google, Nvidia for elite engineering; or a fundable founder — see
|
|
45
|
+
top-companies.md) over vague placeholders like "a serious company with serious
|
|
46
|
+
backing". Only name what the evidence genuinely supports.
|
|
47
|
+
|
|
48
|
+
10. **No grandiose or unfalsifiable claims.** Recognition has to be true and
|
|
49
|
+
checkable. Avoid savior / once-in-history framing and sweeping absolutes ("the
|
|
50
|
+
world would be safe in your hands", "incorruptible", "you will change
|
|
51
|
+
everything"). Everyone is fallible; an over-claim breaks trust instantly, and it
|
|
52
|
+
is not what makes someone feel seen anyway. Stay genuine and grounded in who they
|
|
53
|
+
actually are. Reach high, but only as far as the evidence holds.
|
|
54
|
+
|
|
55
|
+
The test: read it aloud. If it sounds like a human who knows this person wrote it
|
|
56
|
+
plainly, it passes. If it sounds like a model performing insight, rewrite it.
|