# Duplication, rants and outcomes — meeting-time analysis (ESTIMATES)

Scope: same 16 meetings as the agenda/time-split report (last 4 per series; Marketing Weekly 12 Aug–3 Sep, Biz-Dev 23 Sep–14 Oct, Communications 30 Sep–22 Oct, Core Team 5–26 Oct) + Operations Call 19 Oct as an extra (not in averages). Repetition is checked against all 53 earlier-or-same-period transcripts available in `/workspace/mt/` (13 Jul–26 Oct). Everything below is a heuristic estimate, not a measurement.

## 1. Rubric
One label per ~1-min Gemini timestamp block, durations summed. Existing block labels were reused (A/G/J/T); only A blocks were re-split and some A/J/T blocks became rants.
- **Agenda – new:** agenda-item discussion that is not flagged as repetition.
- **Agenda – repeat (pure repetition):** an agenda block whose subject was already a substantive topic (>=3 blocks) in >=2 earlier meetings AND (a) its TF-IDF similarity to the most similar earlier block on that topic is >= 0.15 (STRICT; 0.10 = LOOSE upper bound) AND (b) it contains fewer than 2 decision/commitment phrases ("I'll…", "let's…", "we're going to…", "action item", "decided"…). I.e. re-discussion with no new decision language and wording close to earlier talk. It cannot prove 'no new information'.
- **Agenda – recap for newcomers:** a repeat block in a meeting where advisors/new people were on the call and Ashton was explaining background to them (5 Oct whole meeting; 12 Oct until the advisors left at ~59 min; or explicit cue phrases such as 'for those who', 'as you know', 'remind').
- **Small talk, Adjacent, Tangent:** unchanged from the previous report.
- **Rant / venting:** a stretch (>= ~45 s) where one speaker mainly complains or vents emotion (load, frustration, exasperation) and no decision/action follows in that block. Picked from an emotion-keyword scan of all blocks and then read by me; a rant replaces the earlier A/J/T label for that block, so there is no double counting. Tangents (off-topic lore/anecdotes) remain tangents unless the content is complaint.
- Repetition is only measured inside agenda blocks, so repeats hidden in adjacent/tangent time (e.g. the quiet-vs-loud argument recurring in tangents) are not counted -> the repeat number is a floor.

## 2. Revised split per meeting (% of meeting time)

| Date | Series | Min | Agenda new | Agenda repeat | Recap | Small talk | Adjacent | Tangent | Rant | Repeat (loose upper) | Rant (possible upper) |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-10-05 | Core Team | 185 | 90.1 | 0.0 | 3.3 | 1.9 | 3.2 | 0.5 | 1.0 | 8.2 | 2.6 |
| 2026-10-12 | Core Team | 91 | 73.3 | 1.1 | 2.2 | 6.1 | 14.3 | 0.0 | 2.9 | 10.0 | 2.9 |
| 2026-10-19 | Core Team | 104 | 72.0 | 20.1 | 0.0 | 3.0 | 1.8 | 0.0 | 3.2 | 29.9 | 8.7 |
| 2026-10-26 | Core Team | 63 | 76.3 | 5.2 | 0.0 | 11.5 | 7.1 | 0.0 | 0.0 | 19.9 | 0.0 |
| 2026-09-23 | Biz-Dev | 69 | 46.4 | 0.0 | 0.0 | 4.8 | 44.8 | 0.0 | 4.0 | 1.4 | 9.5 |
| 2026-09-30 | Biz-Dev | 86 | 69.4 | 1.2 | 0.0 | 10.4 | 19.0 | 0.0 | 0.0 | 2.3 | 2.3 |
| 2026-10-07 | Biz-Dev | 87 | 38.9 | 8.3 | 0.0 | 24.3 | 5.7 | 22.8 | 0.0 | 12.7 | 1.9 |
| 2026-10-14 | Biz-Dev | 17 | 80.4 | 0.0 | 0.0 | 0.0 | 7.3 | 0.0 | 12.3 | 0.0 | 12.3 |
| 2026-09-30 | Communications | 73 | 30.2 | 0.0 | 1.3 | 0.0 | 66.0 | 2.5 | 0.0 | 1.3 | 5.4 |
| 2026-10-07 | Communications | 83 | 62.9 | 8.5 | 0.0 | 3.6 | 23.9 | 0.0 | 1.0 | 14.2 | 3.4 |
| 2026-10-14 | Communications | 65 | 49.1 | 17.6 | 0.0 | 1.3 | 32.0 | 0.0 | 0.0 | 17.6 | 1.7 |
| 2026-10-22 | Communications | 63 | 11.6 | 1.8 | 0.0 | 4.3 | 5.6 | 73.1 | 3.6 | 3.6 | 3.6 |
| 2026-08-12 | Marketing | 70 | 69.7 | 0.0 | 0.0 | 0.0 | 30.3 | 0.0 | 0.0 | 4.1 | 0.0 |
| 2026-08-26 | Marketing | 89 | 41.8 | 0.0 | 0.0 | 1.6 | 25.2 | 29.3 | 2.1 | 2.3 | 7.6 |
| 2026-09-02 | Marketing | 85 | 77.7 | 0.0 | 0.0 | 6.3 | 7.3 | 8.7 | 0.0 | 5.7 | 3.0 |
| 2026-09-03 | Marketing | 135 | 68.6 | 5.2 | 0.0 | 12.3 | 13.8 | 0.0 | 0.0 | 7.0 | 1.7 |
| 2026-10-19 | Operations (extra) | 18 | 89.5 | 10.5 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 29.1 | 0.0 |

## 3. Per-series averages (mean of the 4 meetings; duration-weighted in brackets)

| Series | Agenda new | Agenda repeat | Recap | Small talk | Adjacent | Tangent | Rant | Repeat total strict / loose | Rant possible upper |
|---|---|---|---|---|---|---|---|---|---|
| Core Team | 77.9 (80.4) | 6.6 (5.7) | 1.4 (1.8) | 5.6 (4.4) | 6.6 (5.7) | 0.1 (0.2) | 1.8 (1.8) | 8.0 / 17.0 | 3.5 |
| Biz-Dev | 58.8 (53.7) | 2.4 (3.2) | 0.0 (0.0) | 9.9 (12.9) | 19.2 (20.6) | 5.7 (7.7) | 4.1 (1.9) | 2.4 / 4.1 | 6.5 |
| Communications | 38.4 (39.9) | 7.0 (6.9) | 0.3 (0.3) | 2.3 (2.3) | 31.9 (32.5) | 18.9 (16.9) | 1.1 (1.1) | 7.3 / 9.2 | 3.5 |
| Marketing | 64.4 (64.5) | 1.3 (1.9) | 0.0 (0.0) | 5.1 (6.2) | 19.1 (18.1) | 9.5 (8.9) | 0.5 (0.5) | 1.3 / 4.8 | 3.1 |
| ALL | 59.9 (62.5) | 4.3 (4.4) | 0.4 (0.7) | 5.7 (6.1) | 19.2 (17.5) | 8.6 (7.5) | 1.9 (1.3) | 4.7 / 8.8 | 4.2 |

**Overall (16 meetings, ~22.8 h): agenda-new ~60%, agenda-repeat ~4% (+0.4% recap), small talk ~6%, adjacent ~19%, Ashton tangent ~9%, rant ~2%.** Plausible ranges: repetition 5% (strict) to 9% (loose) of all time, and it is a floor; rants 2% (strict, read) to ~4% (incl. unreviewed keyword candidates). Previous 'agenda 66%' = new 60% + repeat/recap 5% + ~2% that became rants.

Notable meetings: Core 19 Oct has the most agenda repetition (20% strict, ~30% loose) — a re-run of the 5 Oct 'quiet vs loud / shared reality' debate and the Farcaster/decentralised-platform argument; Communications 14 Oct 18% (hooks/messaging, content-library and badge flows re-explained); Biz-Dev 7 Oct 8% repeat on top of 23% tangent and 24% small talk; Biz-Dev 14 Oct has the highest rant share (12%, Ashton on being pulled in all directions).

## 4. Recurring topics (top 10 by number of meetings) — dates, status, quotes

Counted over all 53 transcripts; 'substantive' = topic took >=3 blocks in a meeting. Status is my reading of the transcripts and Gemini next steps as of 26 Oct. Chart: `v2_c_top_repeated_topics.png`.

| # | Topic | Meetings (>=3 blocks) | First substantive -> last | Resolved? | Evidence / quotes |
|---|---|---|---|---|---|
| 1 | Creative contest / badges / voting | 19 | 13 Jul -> 14 Oct | Ritual that is re-decided monthly; stop-gap only | 19 Oct Amanda built 'a temporary creative contest voting system' in Excel 'until Fritz decides…'; 14 Oct first monthly badge ceremony proposed on Snapshot. |
| 2 | Web2 demo vs web3 build | 18 | 13 Jul -> 26 Oct | Direction mostly settled (Web2 first), naming/scope still discussed | 5 Oct: "There's basically three choices. Web two, web three, and web 4… we're talking right now about implementing a web two system." 19 Oct roles list gives Thomas 'Development (Web2 Demo)'. 26 Oct: a few minutes on 'demo' vs 'prototype' — "I'll make a final decision on it later… It doesn't matter." (Gemini: team 'indifferent'). |
| 3 | SPEC token allocation / vesting | 17 | 13 Jul -> 26 Oct | Decision made 19 Oct; execution open | 19 Oct: "we're going to bump everybody's allocation by 25%"; 12 Oct 'team token allocation adjustments, we have to talk about this'; 26 Oct a separate 'SPEC token optimization' session set for Thursday 10:00; addresses still being collected. |
| 4 | Content library / announcements / pinned post | 13 | 15 Jul -> 14 Oct (agenda again 22 Oct) | Open | 7 Oct action 'Dzeki & Ashton: work on SP Content Library structure'; 22 Oct agenda leads with 'SP Content Library', 'Voice channel', 'Badge awards' — none discussed (meeting became a book lecture). |
| 5 | Meeting schedule / calendar / reorganising meetings | 12 | 13 Jul -> 26 Oct | Partly: moved to Thursdays 14 Oct, Ops call created 19 Oct, 'access-gated' calendar deferred | 14 Oct Gemini: 'Ashton flagged that management meetings require a separate administrative calendar… deferred final arrangements to the next Monday meeting'; 19 Oct: whole Ops Call 1 (18 min) + ~15 min of Core on re-shuffling meeting slots. |
| 6 | Platform choice (Slack/Discord/Farcaster/Nostr/FROSTR) | 10 | 15 Jul -> 19 Oct (22 Oct agenda) | Slack-vs-Discord settled 12 Oct; rest open | 12 Oct: "Discord gets us everything that we need. Is that good?" -> "Yeah, both work." 7 Oct FROSTR 'Verdict: it's too early'; 19 Oct Farcaster 'techno-optimist pledge' + research task; 22 Oct agenda 'I'm in favor of Nostr only'. |
| 7 | Hiring a PM / manager / CEO / BD person | 10 | 27 Jul (first 'project manager') / 3 Aug (substantive) -> 26 Oct | NOT resolved | 10 Aug: "We don't have a a true project manager."; 30 Sep->7 Oct roles to be posted; 5 Oct: "we're looking for a… manager basically… somebody has to manage the project"; 12 Oct: "We're still really looking for a great project manager." (said twice); 14 Oct Fritz to 'continue search' for BD lead; 26 Oct agenda again 'Open roles discussion…timelines'. |
| 8 | Pitch deck / investor outreach / fundraise | 9 | 23 Jul -> 7 Oct (deadline set 14 Oct) | NOT resolved | 23 Jul Dzeki: "we need to make pitch deck"; 24 Jul Ashton: "So how can we contact them without a pitch deck?"; 7 Oct 'Revisiting the pitch deck task'; 14 Oct Gemini: 'pitch deck finalization targeted for the end of November'. |
| 9 | Shared reality / quiet-vs-loud / cabal / scapegoat narrative | 6 | 10 Aug -> 26 Oct (also 22 Oct lecture) | NOT resolved | 19 Oct: "I keep flip-flopping between the two"; "I don't have an answer, guys… This like breaks my brain". Same argument as 5 Oct agenda item 'Quiet or loud?'. |
| 10 | Ashton overload / offload / delegate (managerial burden) | 2 | mentions in 16 meetings; >=3 blocks 3 Aug & 12 Oct | Partly: Juba offboarded 5 Oct, Ops Call 1 assigned roles 19 Oct; burden restated 14 Oct | 23 Sep: "It all falls on me… it's the managerial stuff"; 5 Oct: "if there's one thing that I can't handle, it's all the interpersonal stuff… this is my worst side"; 12 Oct: "I can't play the manager game also. I also get exploited…"; 14 Oct: "I have to do like the token vesting… and then I have like a million people messaging me." |

Date caveat: first-seen dates for broad topics hit the first transcript (13 Jul) so 'first substantive' is more meaningful; Juba's departure (decided 5 Oct, exit interview reported 14 Oct) and Vatan/community-manager role (16 Sep -> 7 Oct, trial 'second half of October') are resolved/short-lived items not in the top 10.

## 5. Rants (venting without a decision) — who and where

All detected rants are by **Ashton** (about 21 min, ~2% of the 16 meetings; up to ~4% if unreviewed keyword-flagged blocks are counted). I found no rant-length venting by Fritz, Dzeki or Amanda (Eric Dixon's 'trying to teach trigonometry to a pig' remark is one sentence). Rants are about: (1) load/managerial burden and being the single point of failure; (2) frustration with outsiders/communities 'wasting my time'; (3) confusion about how to handle people. Examples (quote, meeting, time ≈ block start):
- 23 Sep BD (≈4–7 min, ≈23 min): "It all falls on me and it's preventing me from actually… it's the managerial stuff"; "I have a f****** million things… if it's not urgent don't message me".
- 26 Aug Marketing (≈40 min): "…causing a lot of f****** b******* and wasting my time on like idiotic debates."
- 5 Oct Core (≈105–108 min): "…there's more stuff to do… all the interpersonal stuff like the management stuff… this is my worst side"; "I wake up… I'm always thinking about this stuff".
- 12 Oct Core (≈56–58 min): "I can't play the manager game also. I also get exploited by… all sorts of different people."
- 14 Oct BD (≈10–13 min): "…when I'm being pulled in all directions and having to think about like everybody's problems…"; "I feel quite like physically isolated."
- 19 Oct Core (≈50–58 min): "the thing that drives me crazy absolutely insane is… these shared realities"; "I don't have an answer, guys. my brain… breaks my brain."
- 22 Oct Comms (≈42, 48 min): "I thought this was fairly straightforward but it turns out that it's… highly complex and I guess I don't know how to deal with people" (inside a 73% tangent meeting).
Not counted as rants: opinionated rants about platforms ('all the Farcaster clients f****** suck') that fed an argument/decision.

## 6. Outcomes vs time

Evidence base: Gemini's 'Decisions' and 'Next steps' sections for each meeting (owner and any date are as Gemini captured them), plus Notion agenda action items. These are Gemini's extraction, so they under- or over-state what was really agreed; treat counts as indicative.

| Date | Series | Min | Next steps | Named owner | Ashton owner | With a date | 'Aligned' decisions | Steps/hour | Ashton talk min | % of Ashton talk in blocks linked to a step/decision (proxy) | Ashton hedges /1000 words |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-10-05 | Core Team | 185 | 18 | 12 | 6 | 2 | 4 | 5.9 | 143.2 | 23.1 | 2.1 |
| 2026-10-12 | Core Team | 91 | 15 | 11 | 5 | 4 | 5 | 9.9 | 79.5 | 40.1 | 1.3 |
| 2026-10-19 | Core Team | 104 | 9 | 7 | 4 | 2 | 4 | 5.2 | 83.6 | 19.3 | 2.8 |
| 2026-10-26 | Core Team | 63 | 9 | 8 | 4 | 0 | 6 | 8.6 | 57.2 | 27.0 | 1.9 |
| 2026-09-23 | Biz-Dev | 69 | 14 | 12 | 3 | 2 | 4 | 12.1 | 60.6 | 42.6 | 3.7 |
| 2026-09-30 | Biz-Dev | 86 | 16 | 14 | 5 | 1 | 7 | 11.1 | 65.1 | 48.2 | 3.3 |
| 2026-10-07 | Biz-Dev | 87 | 11 | 10 | 3 | 2 | 4 | 7.6 | 73.0 | 34.7 | 2.6 |
| 2026-10-14 | Biz-Dev | 17 | 5 | 4 | 2 | 2 | 1 | 17.8 | 15.6 | 76.0 | 3.7 |
| 2026-09-30 | Communications | 73 | 6 | 5 | 3 | 2 | 3 | 4.9 | 61.3 | 22.2 | 3.1 |
| 2026-10-07 | Communications | 83 | 15 | 13 | 2 | 3 | 4 | 10.8 | 61.8 | 36.1 | 3.7 |
| 2026-10-14 | Communications | 65 | 12 | 12 | 4 | 2 | 4 | 11.1 | 54.1 | 56.6 | 2.7 |
| 2026-10-22 | Communications | 63 | 4 | 3 | 1 | 0 | 1 | 3.8 | 57.7 | 15.7 | 3.2 |
| 2026-08-12 | Marketing | 70 | 13 | 8 | 5 | 1 | 8 | 11.2 | 52.9 | 44.9 | 2.2 |
| 2026-08-26 | Marketing | 89 | 10 | 8 | 3 | 1 | 8 | 6.7 | 67.5 | 31.4 | 2.2 |
| 2026-09-02 | Marketing | 85 | 12 | 10 | 4 | 2 | 6 | 8.5 | 66.3 | 38.5 | 2.7 |
| 2026-09-03 | Marketing | 135 | 14 | 13 | 8 | 3 | 13 | 6.2 | 105.4 | 43.2 | 3.0 |
| 2026-10-19 | Operations (extra) | 18 | 5 | 5 | 2 | 0 | 3 | 16.3 | 14.9 | 65.7 | 3.1 |

**Headline numbers (16 meetings, ~22.8 h):** 183 next steps recorded (~8 per hour), 150 with a named person, only 29 (16%) with any date/deadline wording, 82 'aligned' decisions and 7 'needs further discussion'. Ashton is named owner of 62 steps (34%). Ashton spoke ~82% of all words (about 192k of 234k). Only ~37% (mean of meetings; range 16–76%) of his speaking time falls in blocks that match something Gemini later logged as a step or decision — i.e. roughly 6 in 10 minutes of his talk time is not traceable to any recorded outcome (proxy: it links each recorded step to its best-matching blocks, so it is generous). Lowest: Communications 22 Oct 16% (one meeting, 4 steps, none dated), Core 5 Oct 23% (3 h, 18 steps), Communications 30 Sep 22%; highest are the short ones (BD 14 Oct 76%, Ops 19 Oct 66%).

Hedging/deferral phrases ('I don't know', 'I'm not sure', 'I guess', 'no idea', 'figure out', 'we'll see', 'I'm confused'): Ashton 2.6 per 1,000 words vs Fritz 1.0 and Dzeki 1.7 over the same meetings (Amanda 5.9 on only ~1,300 words). This only shows that Ashton's rate is higher than the two comparators', not that he lacks knowledge.

### 6a. Were last meeting's action items done, or just re-discussed?

Method: for each of the 16 meetings I took the same series' previous meeting's Gemini next steps (214 steps; 64 owned by Ashton) and looked in the later meeting for (i) the same step re-listed (text similarity >= 0.30), (ii) a closely matching block (>= 0.12), (iii) explicit completion language. Full list: `action_carryover.csv`.
- **Re-listed as a new next step:** 20/214 (9%); Ashton-owned 6/64 (9%).
- **Discussed again with no completion evidence:** 17/214 (8%); Ashton-owned 5/64 (8%).
- **No trace in the next meeting (neither reported done nor discussed):** 177/214 (83%); Ashton-owned 53/64 (83%). This is 'no evidence', not 'not done' — work may have happened off-call.
- **Explicit completion statements found:** only ~3 (e.g. 19 Oct Ashton: "I did the math on the token allocations for the team"; 14 Oct: "I posted it into the communications channel" re hooks; 12 Oct: first quarterly review 'that we did'). So progress is almost never reported back in the next meeting.
Concrete cases: **Hire Project Manager** (Ashton, 5 Oct) -> 12 Oct "We're still really looking for a great project manager" (re-discussed; open). **Create Mind Map** (Ashton, 5 Oct) -> the phrase 'mind map' does not appear in the 12, 19 or 26 Oct transcripts. **Create Pitch Deck** (Ashton, 7 Oct) -> re-listed 14 Oct as 'Finalize Pitch Deck… end of November', while the same meeting has him saying he could make it "in like three days" if not "pulled in all directions". **Post Job Roles / Advertise roles** (30 Sep, 7 Oct) -> 12 Oct still looking; 14 Oct Fritz to 'continue the search'. **Submit presentation ideas / Apply to conference** (23 Sep) -> re-listed 30 Sep and 7 Oct, then 14 Oct 'conferences avoided as time sinks'. **Record Tescow Lessons** — an action item assigned to Ashton on 7 Oct comes from the martial-arts tangent (a tangent leaking into the action list) and never reappears.

### 6b. Where Ashton is vague, contradicts, or defers (evidence only)
- **Vague / no landing:** 22 Oct: "Anyways, I don't know what else to say other than the people aren't who I expected… I don't really know what to…" (end of a ~60 min lecture; Gemini records 4 next steps, none dated, 'post the book link' being the Ashton one). 19 Oct: "I don't have an answer, guys… This breaks my brain" on quiet vs loud.
- **Contradiction / tension with earlier statements:** 5 Oct: "I noticed myself instinctively taking control… we need to delegate his responsibilities" vs 26 Oct: "…offload my responsibilities to them. First of all, they're not going to do that great of a job." 19 Oct "I keep flip-flopping between the two" (quiet vs loud) after presenting it as an agenda decision on 5 Oct. Pitch-deck timing: 'three days' (14 Oct) vs 'end of November' (14 Oct next step).
- **Deferral / delegation:** 7 Oct (Comms): "I'll let you kind of decide on that at the moment" (Fritz); 26 Oct: "I'll make a final decision on it later. We can just move on… It doesn't matter" (demo vs prototype naming after a few minutes); 14 Oct (Comms): "for marketing, that's your thing. Like you should be able to handle that without much like interference from me"; 14 Oct: "I feel like we spend too much time talking about all this" — about the AI-bot-for-Discord discussion that took ~20 min of that meeting (adjacent, no decision).
- **Time without outcome (examples):** 7 Oct BD ~20 min small talk (sleep/cortisol, gym advice) + ~20 min martial-arts lecture before the agenda; 22 Oct Comms none of the first listed Notion agenda items (content library, voice channel, badge awards, podcast template…) were discussed; 5 Oct Core 3 h 5 min with 18 recorded steps (6 'group'-owned, 2 dated).
I make no claim about the accuracy of his knowledge — only the quoted vagueness/deferral/tension.

## 7. Caveats
- Repetition is detected by topic keywords + TF-IDF similarity + absence of decision words; it misses paraphrased repeats and anything in adjacent/tangent blocks, and my spot-check of ~24 flagged blocks judged roughly 55–65% as genuine re-discussion. Hence strict 4.7% (floor) and loose 8.8% (upper) rather than a point value. 'Without new information' can't be verified automatically.
- Rants were found with a keyword scan (profanity, 'annoying', 'can't handle', etc.) and then read; calm complaints without those words are likely missed. Reported strict number includes only blocks I read; 'possible upper' adds unreviewed keyword-dense blocks.
- Outcome counts depend on Gemini's note-taking (owners/dates are often missing in speech); the 'linked to a step' share is a proxy. 83% 'no trace' means no textual evidence in the next meeting, not proof of non-completion.
- Compared transcripts: 53 files; the first meetings (Jul) have little history to repeat against, so Marketing's repeat share is structurally low.
- Block labels are one-per-minute and mixed blocks are rounded; ±10 points per meeting plausible. Machine-generated transcripts and speaker labels have errors.
- Ops Call 19 Oct shows 29% 'loose' repeat: it re-lists roles/calendar items already discussed 14 Oct, but it is excluded from averages.

## 8. Files
- `report_repetition_rants.md` (this report)
- `meetings.csv` (updated: v2 columns `v2_pct_*`, outcome columns; original in `meetings_v1.csv`), `series_summary_v2.json`, `rows_v2.json`
- `action_carryover.csv`, `topic_rank.json`, `segments_labels.csv`
- Charts: `v2_a_overall_pie.png`, `v2_b_series_stacked100.png`, `v2_b2_per_meeting_stacked100.png`, `v2_c_top_repeated_topics.png`, `v2_d_outcomes.png`
- Code: `dup2.py`, `final.py`, `charts2.py`, `outc2.py`, `hedge.py`, `rant1.py`