Skip to content

Decide fate of "Block to the Future" / Future Patterns section (L719–791) #96

Description

@MaggieAppleton

Parent plan

#92

What to build

Make an editorial decision on the weakest section of the essay, then implement it in src/content/essays/block-party.mdx:

Primary recommendation (from plan): Delete the entire "Block to the Future" section (L719–791). The essay has a complete arc without it; the section is speculative, formatting is broken (<ListNumber> missing on items 4–7), item 6 is duplicated, and a full AI chapter isn't planned. End at "A History of Blocks" with a brief outro paragraph.

Alternative: Keep only items 1, 2, and 5 properly formatted in <ListNumber> components, cut the rest (items 3, 4, 6, 7), and fix the duplicate item 6.

Either path also needs:

  • The Hash disclaimer already moved to its new position (see sub-issue for structural housekeeping) means the old L723–735 block is gone regardless.
  • An outro paragraph added at the end of "A History of Blocks" if the section is deleted.

Acceptance criteria

  • Section either deleted entirely or trimmed to items 1, 2, 5 with correct <ListNumber> formatting
  • No broken plain-markdown numbered items remain where <ListNumber> is expected
  • No duplicate item 6
  • If deleted: a brief closing paragraph is added after the "A History of Blocks" section
  • File renders without MDX errors

Blocked by

None — can start immediately (but coordinate with structural housekeeping issue re: disclaimer removal)

Open questions

  • Delete vs. trim? Plan recommends full deletion; the alternative preserves items 1, 2, 5. Maggie should confirm which path before this is implemented.
  • Outro paragraph: If the section is deleted, is a single closing sentence enough, or does it need a fuller paragraph tying back to the intro?
    Related to Block Party essay cleanup checklist #92

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub integrity level.

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Plan issue → sub-issues for issue #92 · ● 187.5K ·

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions