docs(exploration): add AFFiNE BlockSuite integration feasibility analysis

[crs48]

Summary\n- add exploration 0102 for AFFiNE BlockSuite integration feasibility\n- capture architecture fit, risks, and implementation considerations\n- place document under docs/explorations for review and follow-up planning\n\n## Testing\n- not applicable (documentation-only change)

Summary by CodeRabbit

• Documentation
  • Added a comprehensive feasibility exploration evaluating integration with an external suite, covering problem statements, architectural comparisons, data-model and feature overlap analyses, identified conflicts and risks, recommended integration strategies, component-reuse guidance, React API considerations, adapter-layer technical deep dives, mitigation approaches, and a phased implementation roadmap with milestones and validation criteria.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 48fd73c2-913e-4dc1-9692-6f872c25d3c7

📥 Commits

Reviewing files that changed from the base of the PR and between 8b23d7e and 3753f67.

📒 Files selected for processing (1)

• docs/explorations/0102_[_]_AFFINE_BLOCKSUITE_INTEGRATION_FEASIBILITY.md

---

📝 Walkthrough

Walkthrough

A comprehensive feasibility exploration document has been added that evaluates integrating AFFiNE/BlockSuite with xNet. The analysis covers architectural compatibility, identifies key conflicts (CRDT mismatch, storage paradigms, authorization gaps), compares feature overlaps, and recommends selective UX borrowing over full integration.

Changes

Cohort / File(s)	Summary
Feasibility Exploration docs/explorations/0102_[_]_AFFINE_BLOCKSUITE_INTEGRATION_FEASIBILITY.md	Added a ~1066-line feasibility study detailing problem statements, architecture comparisons, data-model mismatches, feature overlap scoring, critical conflicts, integration strategies (Full Adoption, UI Components Only, Reference Implementation), adapter design, implementation roadmap, risk assessment, validation criteria, and appendices.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped through lines of plans and schemes,
To ponder merging canvases and dreams.
Where CRDTs clash and storages part,
I nibbled ideas, kept the best art.
Select the sparkle, keep the heart. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and accurately summarizes the main change: adding a detailed feasibility analysis document for AFFiNE BlockSuite integration to the explorations directory.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/pr-0102-affine-blocksuite

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This PR adds a thorough 1,066-line exploration document evaluating whether AFFiNE/BlockSuite can power xNet's docs, canvas, and database features. The document correctly identifies fundamental incompatibilities (CRDT data models, event-sourced vs. IndexedDB storage, workspace-level vs. node-level authorization) and recommends selective UX borrowing over full integration, backed by architecture diagrams, a phased roadmap, and a component-extraction checklist.

Key items:

• The analysis is well-structured and the strategy recommendations (Strategy B for near-term component extraction, Strategy C as long-term reference implementation) are sound and internally consistent.
• One editorial issue remains: the Product Risks table contains two contradictory rows for the same "Legal issues" risk — the original incorrect row (MPL 2.0 labeled as "permissive", severity 🟢 Low) was not removed when the corrected row (weak copyleft, 🟡 Medium) was added as a follow-up to a prior review. This leaves the table self-contradictory and should be resolved by deleting the stale first row.

Confidence Score: 3/5

• Safe to merge after the duplicate risk-table row is resolved; document is documentation-only with no code impact.
• The document is thorough and technically sound. The only blocking concern is the duplicate "Legal issues" row in the Product Risks table, which leaves an incorrect entry (MPL 2.0 as "permissive", 🟢 Low severity) alongside the corrected one — a direct internal contradiction that should be cleaned up before merging to avoid misleading future readers.
• The risk assessment table in docs/explorations/0102_[_]_AFFINE_BLOCKSUITE_INTEGRATION_FEASIBILITY.md (lines 816–817) needs the stale duplicate row removed.

Important Files Changed

Filename

Overview

docs/explorations/0102_[_]_AFFINE_BLOCKSUITE_INTEGRATION_FEASIBILITY.md

Comprehensive 1,066-line feasibility analysis for AFFiNE/BlockSuite integration, covering architecture comparison, three integration strategies, component reuse priorities, a phased roadmap, and risk assessment. One structural issue: the Product Risks table contains a duplicate "Legal issues" row — the original incorrect row (MPL 2.0 labeled permissive, severity 🟢 Low) was not removed when a corrected row was added, creating a direct internal contradiction.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    Start([Evaluate AFFiNE/BlockSuite Integration])
    Start --> Q1{Need full editor\nreplacement?}

    Q1 -- Yes --> StratA[Strategy A: Full Adoption]
    StratA --> A_result[❌ Not Viable\nBreaks event sourcing,\nschema system, auth model]

    Q1 -- No --> Q2{Need actual\nBlockSuite code?}

    Q2 -- Yes --> StratB[Strategy B: UI Components Only]
    StratB --> B_result[✅ Recommended\nCherry-pick widgets,\nwire to xNet hooks]
    B_result --> Adapter[Thin adapter layer:\nCommand / Event / State mappers]
    Adapter --> xNetCore[xNet Core Unchanged:\nevent sourcing · schema · UCAN auth]

    Q2 -- No --> StratC[Strategy C: Reference Implementation]
    StratC --> C_result[✅ Best Long-Term\nStudy UX patterns,\nrebuild natively]
    C_result --> NativeUI[Native components:\nTailwind + Base UI\nZero BlockSuite dependencies]
    NativeUI --> xNetCore

    xNetCore --> Deploy([Ship AFFiNE-inspired UX\nwith xNet architecture intact])

Loading

_{Last reviewed commit: 3753f67}

[greptile-apps]

Duplicate "Legal issues" row — original incorrect entry not removed

The Product Risks table now has two consecutive rows for the same risk. It looks like the corrected row (line 817) was appended when addressing a previous review comment, but the original row (line 816) — which still carries the incorrect (permissive) label and an inconsistent 🟢 Low severity — was never removed. This leaves the table contradicting itself: the same risk is rated both 🟢 Low and 🟡 Medium.

The first row should be deleted so only the corrected entry remains:

Suggested change

	### Immediate Actions (This Week)
	| **Legal issues** - License or trademark concerns | 🟡 Medium | BlockSuite is MPL 2.0 (weak copyleft, file-level); do not copy source files — copy only visual patterns and interactions |