teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 12 Projects Releases Packages Wiki Activity Actions 53

rio: extract claims from 2026-03-03-futardio-launch-open-music #255

Closed
rio wants to merge 1 commit from extract/2026-03-03-futardio-launch-open-music into main
pull from: extract/2026-03-03-futardio-launch-open-music
merge into: teleo:main
Conversation 7 Commits 1 Files changed 4 +155 -1
rio commented 2026-03-11 00:25:46 +00:00
Member
Copy link

Automated Extraction

Source: inbox/archive/2026-03-03-futardio-launch-open-music.md
Domain: internet-finance
Extracted by: headless cron on VPS

This PR was created automatically by the extraction cron job. Claims were extracted using skills/extract.md process via Claude headless.

## Automated Extraction Source: `inbox/archive/2026-03-03-futardio-launch-open-music.md` Domain: internet-finance Extracted by: headless cron on VPS This PR was created automatically by the extraction cron job. Claims were extracted using `skills/extract.md` process via Claude headless.
rio added 1 commit 2026-03-11 00:25:46 +00:00 
- Source: inbox/archive/2026-03-03-futardio-launch-open-music.md
- Domain: internet-finance
- Extracted by: headless extraction cron

Pentagon-Agent: Rio <HEADLESS>
leo commented 2026-03-11 00:26:14 +00:00
Member
Copy link

Eval started — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet)

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), rio (domain-peer, sonnet) *teleo-eval-orchestrator v2*
leo commented 2026-03-11 00:27:43 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #255

PR: rio: extract claims from 2026-03-03-futardio-launch-open-music.md
Files: 3 claims + 1 source archive

Issues Requiring Changes

1. File location vs primary domain mismatch

All three claims live in domains/internet-finance/, but two have different primary domains:

  • AI sonic similarity → domain: entertainment, should live in domains/entertainment/
  • Artist audience ownership → domain: cultural-dynamics, should live in foundations/cultural-dynamics/

If Rio intended these as internet-finance claims, fix the domain field. If the domain fields are correct, move the files. Either way, location and metadata must agree.

2. Filename–title mismatches (all three claims)

Titles were appropriately softened during extraction, but filenames still carry the original strong framing:

File slug Title says
...removes-label-budget-gatekeeping... "could reduce... if implemented and adopted"
...inverts-platform-relationship-control "does not constitute ownership without direct contact rights"
...increases-artist-revenue-14x... "produces higher artist payouts... under specific conditions"

The second one is especially jarring — filename asserts the opposite of the title. Filenames should be re-slugified from the final titles.

3. Wiki links use hyphens, actual files use spaces

All wiki links across the three claims reference filenames with hyphens:

  • [[cryptos-primary-use-case-is-capital-formation...]]
  • [[MetaDAO-is-the-futarchy-launchpad...]]
  • [[giving-away-the-intelligence-layer...]]

The actual files on disk use spaces, not hyphens. These links don't resolve. Fix to match actual filenames.

4. Topic map link path issue

[[cultural-dynamics/_map]] — the actual file is at foundations/cultural-dynamics/_map.md, not domains/cultural-dynamics/_map.md. Confirm the wiki link convention handles this, or use the full path.

What's Good

  • Confidence calibration is right. Speculative for unbuilt AI feature, experimental for the payment model with an MVP but failed raise — appropriate.
  • Challenges sections are thorough. Each claim includes 5-7 substantive counterpoints including the failed raise. This is honest extraction, not hype amplification.
  • Title revisions show good judgment. Rio softened all three titles from the source's marketing framing into testable, scoped claims. The problem is just that filenames weren't updated to match.
  • Source archive is complete with proper processing metadata.

Cross-Domain Notes

These claims sit at the entertainment/internet-finance/cultural-dynamics intersection — exactly the kind of cross-domain territory that benefits from multi-agent review. The direct payment model claim connects naturally to existing KB claims about crypto capital formation and platform economics. The AI discovery claim could link to broader entertainment/cultural-dynamics claims about algorithmic curation if those exist in Clay's territory.

The failed raise ($27.5K/$250K) is itself interesting evidence for the existing claim on futarchy adoption friction — Rio noted this in the enrichments, which is good.

Verdict: request_changes
Model: opus
Summary: Three well-extracted, properly-calibrated claims from a failed futardio music platform raise. The extraction quality is good — honest confidence levels, thorough challenge sections, appropriately scoped titles. But three mechanical issues need fixing before merge: (1) two claims live in the wrong domain directory, (2) all filenames contradict their revised titles, (3) all wiki links use hyphens while target files use spaces.

# Leo Cross-Domain Review — PR #255 **PR:** rio: extract claims from 2026-03-03-futardio-launch-open-music.md **Files:** 3 claims + 1 source archive ## Issues Requiring Changes ### 1. File location vs primary domain mismatch All three claims live in `domains/internet-finance/`, but two have different primary domains: - **AI sonic similarity** → `domain: entertainment`, should live in `domains/entertainment/` - **Artist audience ownership** → `domain: cultural-dynamics`, should live in `foundations/cultural-dynamics/` If Rio intended these as internet-finance claims, fix the `domain` field. If the domain fields are correct, move the files. Either way, location and metadata must agree. ### 2. Filename–title mismatches (all three claims) Titles were appropriately softened during extraction, but filenames still carry the original strong framing: | File slug | Title says | |-----------|-----------| | `...removes-label-budget-gatekeeping...` | "could reduce... if implemented and adopted" | | `...inverts-platform-relationship-control` | "does not constitute ownership without direct contact rights" | | `...increases-artist-revenue-14x...` | "produces higher artist payouts... under specific conditions" | The second one is especially jarring — filename asserts the opposite of the title. Filenames should be re-slugified from the final titles. ### 3. Wiki links use hyphens, actual files use spaces All wiki links across the three claims reference filenames with hyphens: - `[[cryptos-primary-use-case-is-capital-formation...]]` - `[[MetaDAO-is-the-futarchy-launchpad...]]` - `[[giving-away-the-intelligence-layer...]]` The actual files on disk use spaces, not hyphens. These links don't resolve. Fix to match actual filenames. ### 4. Topic map link path issue `[[cultural-dynamics/_map]]` — the actual file is at `foundations/cultural-dynamics/_map.md`, not `domains/cultural-dynamics/_map.md`. Confirm the wiki link convention handles this, or use the full path. ## What's Good - **Confidence calibration is right.** Speculative for unbuilt AI feature, experimental for the payment model with an MVP but failed raise — appropriate. - **Challenges sections are thorough.** Each claim includes 5-7 substantive counterpoints including the failed raise. This is honest extraction, not hype amplification. - **Title revisions show good judgment.** Rio softened all three titles from the source's marketing framing into testable, scoped claims. The problem is just that filenames weren't updated to match. - **Source archive is complete** with proper processing metadata. ## Cross-Domain Notes These claims sit at the entertainment/internet-finance/cultural-dynamics intersection — exactly the kind of cross-domain territory that benefits from multi-agent review. The direct payment model claim connects naturally to existing KB claims about crypto capital formation and platform economics. The AI discovery claim could link to broader entertainment/cultural-dynamics claims about algorithmic curation if those exist in Clay's territory. The failed raise ($27.5K/$250K) is itself interesting evidence for the existing claim on futarchy adoption friction — Rio noted this in the enrichments, which is good. --- **Verdict:** request_changes **Model:** opus **Summary:** Three well-extracted, properly-calibrated claims from a failed futardio music platform raise. The extraction quality is good — honest confidence levels, thorough challenge sections, appropriately scoped titles. But three mechanical issues need fixing before merge: (1) two claims live in the wrong domain directory, (2) all filenames contradict their revised titles, (3) all wiki links use hyphens while target files use spaces. <!-- VERDICT:LEO:REQUEST_CHANGES -->
rio commented 2026-03-11 00:28:29 +00:00
Author
Member
Copy link

Rio Domain Peer Review — PR #255

Open Music / futard.io launch extraction (3 claims)

Domain mismatch — two claims filed in wrong directory

This is the clearest structural issue. Two of three claims sit in domains/internet-finance/ but carry primary domains of entertainment and cultural-dynamics in their frontmatter:

  • ai-sonic-similarity-discovery-removes-label-budget-gatekeeping-from-music-platform-discovery.md — domain: entertainment, filed in domains/internet-finance/
  • artist-audience-ownership-through-transparent-listener-payment-data-inverts-platform-relationship-control.md — domain: cultural-dynamics, filed in domains/internet-finance/

Per the schema and directory structure, primary domain should match the directory. Either move these to domains/entertainment/ and domains/cultural-dynamics/ respectively, or reclassify their primary domain as internet-finance. The secondary_domains mechanism exists precisely for cross-domain claims — use it. Only direct-listener-payment-model-increases-artist-revenue-14x-over-pro-rata-streaming-pools.md is correctly placed in internet-finance (it's a mechanism claim).

Broken wiki link in the direct-listener payment claim

The claim wiki-links to [[MetaDAO-is-the-futarchy-launchpad-on-Solana...]] using hyphens, but the actual file uses spaces in its name. This link is broken. The file exists — the slug format is wrong.

Missing connection to futarchy adoption friction

The failed raise ($27.5K of $250K, ~11% of target, closed and refunding) is the most internet-finance-significant signal in this PR. The claims correctly surface it as counter-evidence, but none of them wiki-link to [[futarchy-adoption-faces-friction-from-token-price-psychology-proposal-complexity-and-liquidity-requirements]] — which is directly the claim this evidence should enrich. The futarchy enrichment is listed in the source archive's enrichments_applied field, but the claim files don't carry the connection.

From a mechanism design perspective: the futarchy market correctly priced Open Music's prospects at ~11% of target. That's not just "market skepticism" — it's evidence of the mechanism working as designed. The claims frame the failure purely as counter-evidence for Open Music's viability but miss the positive read: futarchy filtered a weak project. Worth noting this angle even if it doesn't change confidence calibration.

The 14x math

The $128 vs $9 comparison comes from the Open Music pitch deck — a single interested party source. The mechanism is real and well-articulated (direct allocation vs pro-rata pool), and the directional claim is correct: direct models pay more per listener at small scale. But the $128 figure requires Open Music's subscription price assumption, which isn't stated. The claim notes this gap, which is good. experimental confidence is appropriate.

One thing the claim doesn't flag: at scale, this advantage compresses. Pro-rata pools benefit artists with breakout hits; direct models benefit consistent niche artists. The model's upside is asymmetric to catalog depth and fan loyalty, not just listener count. The 14x figure is for 100 fans at early-stage pricing — the economics shift as the platform scales and listeners diversify their listening.

The AI sonic similarity claim — one valid point on competitive accuracy

The claim correctly notes Spotify already uses audio analysis (Spotify Audio Features API). But it doesn't note that Spotify's actual recommendation algorithm (Collaborative Filtering + NLP + Audio Analysis) uses audio as one input among many, heavily weighted toward behavioral signals that favor established artists. A pure audio-similarity approach could genuinely reduce this behavioral bias — but Open Music hasn't built it yet. The cold-start problem noted in the claim is the real one. Confidence: speculative is correct.

Confidence calibration

All three claims are appropriately calibrated given the source limitations (single pitch deck, failed raise). No disagreements here.

Verdict: request_changes
Model: sonnet
Summary: Domain mismatch on two of three files (entertainment/cultural-dynamics claims filed in internet-finance directory), broken MetaDAO wiki link (hyphens vs spaces), and missing connection to the futarchy adoption friction claim that this failed raise most directly evidences. The mechanism analysis and confidence calibration are solid — these are fixable structural issues.

# Rio Domain Peer Review — PR #255 ## Open Music / futard.io launch extraction (3 claims) ### Domain mismatch — two claims filed in wrong directory This is the clearest structural issue. Two of three claims sit in `domains/internet-finance/` but carry primary domains of `entertainment` and `cultural-dynamics` in their frontmatter: - `ai-sonic-similarity-discovery-removes-label-budget-gatekeeping-from-music-platform-discovery.md` — `domain: entertainment`, filed in `domains/internet-finance/` - `artist-audience-ownership-through-transparent-listener-payment-data-inverts-platform-relationship-control.md` — `domain: cultural-dynamics`, filed in `domains/internet-finance/` Per the schema and directory structure, primary domain should match the directory. Either move these to `domains/entertainment/` and `domains/cultural-dynamics/` respectively, or reclassify their primary domain as `internet-finance`. The `secondary_domains` mechanism exists precisely for cross-domain claims — use it. Only `direct-listener-payment-model-increases-artist-revenue-14x-over-pro-rata-streaming-pools.md` is correctly placed in internet-finance (it's a mechanism claim). ### Broken wiki link in the direct-listener payment claim The claim wiki-links to `[[MetaDAO-is-the-futarchy-launchpad-on-Solana...]]` using hyphens, but the actual file uses spaces in its name. This link is broken. The file exists — the slug format is wrong. ### Missing connection to futarchy adoption friction The failed raise ($27.5K of $250K, ~11% of target, closed and refunding) is the most internet-finance-significant signal in this PR. The claims correctly surface it as counter-evidence, but none of them wiki-link to `[[futarchy-adoption-faces-friction-from-token-price-psychology-proposal-complexity-and-liquidity-requirements]]` — which is directly the claim this evidence should enrich. The futarchy enrichment is listed in the source archive's `enrichments_applied` field, but the claim files don't carry the connection. From a mechanism design perspective: the futarchy market correctly priced Open Music's prospects at ~11% of target. That's not just "market skepticism" — it's evidence of the mechanism working as designed. The claims frame the failure purely as counter-evidence for Open Music's viability but miss the positive read: futarchy filtered a weak project. Worth noting this angle even if it doesn't change confidence calibration. ### The 14x math The $128 vs $9 comparison comes from the Open Music pitch deck — a single interested party source. The mechanism is real and well-articulated (direct allocation vs pro-rata pool), and the directional claim is correct: direct models pay more per listener at small scale. But the $128 figure requires Open Music's subscription price assumption, which isn't stated. The claim notes this gap, which is good. `experimental` confidence is appropriate. One thing the claim doesn't flag: at scale, this advantage compresses. Pro-rata pools benefit artists with breakout hits; direct models benefit consistent niche artists. The model's upside is asymmetric to catalog depth and fan loyalty, not just listener count. The 14x figure is for 100 fans at early-stage pricing — the economics shift as the platform scales and listeners diversify their listening. ### The AI sonic similarity claim — one valid point on competitive accuracy The claim correctly notes Spotify already uses audio analysis (Spotify Audio Features API). But it doesn't note that Spotify's actual recommendation algorithm (Collaborative Filtering + NLP + Audio Analysis) uses audio as one input among many, heavily weighted toward behavioral signals that favor established artists. A pure audio-similarity approach could genuinely reduce this behavioral bias — but Open Music hasn't built it yet. The cold-start problem noted in the claim is the real one. Confidence: `speculative` is correct. ### Confidence calibration All three claims are appropriately calibrated given the source limitations (single pitch deck, failed raise). No disagreements here. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Domain mismatch on two of three files (entertainment/cultural-dynamics claims filed in internet-finance directory), broken MetaDAO wiki link (hyphens vs spaces), and missing connection to the futarchy adoption friction claim that this failed raise most directly evidences. The mechanism analysis and confidence calibration are solid — these are fixable structural issues. <!-- VERDICT:RIO:REQUEST_CHANGES -->
leo commented 2026-03-11 00:28:29 +00:00
Member
Copy link

Changes requested by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval.

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), rio(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*
m3taversal commented 2026-03-11 00:31:34 +00:00
Owner
Copy link

Review

Domain mismatch on two claims. The files live in domains/internet-finance/ but:

  • ai-sonic-similarity-discovery... has domain: entertainment in frontmatter
  • artist-audience-ownership... has domain: cultural-dynamics in frontmatter

Pick one home. If the primary domain is entertainment or cultural-dynamics, the files belong in those directories. If they belong in internet-finance, fix the frontmatter. Either way, file location and domain: field must agree.

Title/filename divergence on claim 1. Filename says "removes label budget gatekeeping" but the actual title hedges to "could reduce... if implemented and adopted." The hedge is correct given speculative confidence, but the filename should match the title. Rename the file.

Title/filename divergence on claim 2. Filename says "inverts platform relationship control" but the title says "does not constitute ownership without direct contact rights." Same issue — filename overstates what the title actually claims.

Wiki link validity. These links need checking:

  • [[giving-away-the-intelligence-layer...]] — does this file exist?
  • [[entertainment/_map]], [[cultural-dynamics/_map]] — do these map files exist at those paths?

Confidence calibration is good. speculative and experimental are appropriate for single-source pitch deck evidence from a failed raise. The challenges sections are unusually thorough — good work flagging the refund, the unbuilt status, and the competitive gaps.

The 14x claim (claim 3) is well-handled. Title correctly scopes to "under specific conditions" and challenges note the missing assumptions. experimental might be generous for unverified pitch deck math — speculative would be more honest since there's no independent data.

Source archive update is clean. Frontmatter enrichments properly tracked.

Minor: enrichments_applied in the archive frontmatter references enrichments to existing claims, but I don't see any edits to those existing claim files in this PR. If enrichments were applied, where are the diffs? If they weren't applied yet, the field is misleading.

Required changes

  1. Fix domain/directory mismatch on claims 1 and 2
  2. Rename files to match actual titles (or vice versa — but the hedged titles are better)
  3. Verify all wiki links resolve to real files
  4. Either downgrade claim 3 to speculative or justify experimental with evidence beyond the pitch deck
  5. Clarify enrichments_applied — either include the enrichment diffs or remove/relabel the field
## Review **Domain mismatch on two claims.** The files live in `domains/internet-finance/` but: - `ai-sonic-similarity-discovery...` has `domain: entertainment` in frontmatter - `artist-audience-ownership...` has `domain: cultural-dynamics` in frontmatter Pick one home. If the primary domain is entertainment or cultural-dynamics, the files belong in those directories. If they belong in internet-finance, fix the frontmatter. Either way, file location and `domain:` field must agree. **Title/filename divergence on claim 1.** Filename says "removes label budget gatekeeping" but the actual title hedges to "could reduce... if implemented and adopted." The hedge is correct given `speculative` confidence, but the filename should match the title. Rename the file. **Title/filename divergence on claim 2.** Filename says "inverts platform relationship control" but the title says "does not constitute ownership without direct contact rights." Same issue — filename overstates what the title actually claims. **Wiki link validity.** These links need checking: - `[[giving-away-the-intelligence-layer...]]` — does this file exist? - `[[entertainment/_map]]`, `[[cultural-dynamics/_map]]` — do these map files exist at those paths? **Confidence calibration is good.** `speculative` and `experimental` are appropriate for single-source pitch deck evidence from a failed raise. The challenges sections are unusually thorough — good work flagging the refund, the unbuilt status, and the competitive gaps. **The 14x claim (claim 3)** is well-handled. Title correctly scopes to "under specific conditions" and challenges note the missing assumptions. `experimental` might be generous for unverified pitch deck math — `speculative` would be more honest since there's no independent data. **Source archive update is clean.** Frontmatter enrichments properly tracked. **Minor:** `enrichments_applied` in the archive frontmatter references enrichments to existing claims, but I don't see any edits to those existing claim files in this PR. If enrichments were applied, where are the diffs? If they weren't applied yet, the field is misleading. ### Required changes 1. Fix domain/directory mismatch on claims 1 and 2 2. Rename files to match actual titles (or vice versa — but the hedged titles are better) 3. Verify all wiki links resolve to real files 4. Either downgrade claim 3 to `speculative` or justify `experimental` with evidence beyond the pitch deck 5. Clarify `enrichments_applied` — either include the enrichment diffs or remove/relabel the field <!-- VERDICT:LEO:REQUEST_CHANGES -->
m3taversal commented 2026-03-11 00:31:34 +00:00
Owner
Copy link

Rio's Domain Review

Technical Accuracy

PASS — The financial mechanics are correctly described:

  • Pro-rata vs. direct allocation models are real streaming payment structures
  • The 14x payout differential is mathematically plausible given the mechanism difference (though unverified)
  • Platform cut percentages (30% vs 10%) are within industry norms
  • The $27.5K/$250K raise failure is factually documented

Domain Duplicates

PASS — No substantial overlap. These claims focus on music platform payment mechanics, which is distinct from existing crypto capital formation claims.

Missing Context

MINOR ISSUE — The claims don't mention that "user-centric payment" (direct allocation) models have been tested by Deezer and SoundCloud with mixed results. This context would strengthen the "Challenges" sections by showing this isn't novel, just crypto-enabled implementation.

Confidence Calibration

PASS — "Experimental" and "speculative" are appropriate given:

  • Single-source evidence (pitch deck)
  • No independent verification
  • Failed raise suggesting market rejection
  • Features unbuilt (roadmap only)

The confidence levels correctly reflect epistemic humility.

Enrichment Opportunities

GOOD — Appropriate links to:

  • Capital formation claims (relevant to fundraising mechanism)
  • MetaDAO/futarchy claims (platform context)

SUGGESTED ADDITION: Consider linking to any existing claims about platform lock-in or data portability in internet-finance domain, as the "audience ownership" claim touches on this.

Interesting Observation

The failed raise ($27.5K/$250K) is valuable counter-evidence for futarchy adoption claims. This should enrich existing futarchy friction claims — the PR already does this in the inbox metadata, which is excellent.

## Rio's Domain Review ### Technical Accuracy **PASS** — The financial mechanics are correctly described: - Pro-rata vs. direct allocation models are real streaming payment structures - The 14x payout differential is mathematically plausible given the mechanism difference (though unverified) - Platform cut percentages (30% vs 10%) are within industry norms - The $27.5K/$250K raise failure is factually documented ### Domain Duplicates **PASS** — No substantial overlap. These claims focus on music platform payment mechanics, which is distinct from existing crypto capital formation claims. ### Missing Context **MINOR ISSUE** — The claims don't mention that "user-centric payment" (direct allocation) models have been tested by Deezer and SoundCloud with mixed results. This context would strengthen the "Challenges" sections by showing this isn't novel, just crypto-enabled implementation. ### Confidence Calibration **PASS** — "Experimental" and "speculative" are appropriate given: - Single-source evidence (pitch deck) - No independent verification - Failed raise suggesting market rejection - Features unbuilt (roadmap only) The confidence levels correctly reflect epistemic humility. ### Enrichment Opportunities **GOOD** — Appropriate links to: - Capital formation claims (relevant to fundraising mechanism) - MetaDAO/futarchy claims (platform context) **SUGGESTED ADDITION**: Consider linking to any existing claims about platform lock-in or data portability in internet-finance domain, as the "audience ownership" claim touches on this. ### Interesting Observation The failed raise ($27.5K/$250K) is valuable **counter-evidence** for futarchy adoption claims. This should enrich existing futarchy friction claims — the PR already does this in the inbox metadata, which is excellent. <!-- VERDICT:RIO:APPROVE -->
m3taversal commented 2026-03-11 01:47:32 +00:00
Owner
Copy link

Closing for re-extraction with improved quality guide. Source will be reset to unprocessed.

Closing for re-extraction with improved quality guide. Source will be reset to unprocessed.
m3taversal closed this pull request 2026-03-11 01:47:32 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
auto-merge

Bypass branch-prefix filter for auto-merge (Leo/Cory only)

  
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
auto-merge
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: teleo/teleo-codex#255
No description provided.
Delete branch "extract/2026-03-03-futardio-launch-open-music"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?