docs: sync cross repo advantage plan

2026-07-19 11:40:23 +08:00
parent 82f4862aef
commit e7c11b2aee
4 changed files with 223 additions and 0 deletions
@@ -0,0 +1,52 @@
+# Commercial onboarding UX → research contract — 2026-07-19
+
+Purpose: reuse commercial UX strengths in the research repo without importing business runtime.
+
+## Flow to learn
+
+称呼 → 出生时间 → 出生地点 → 时间校正
+
+Observed commercial strengths:
+
+- conversational first contact instead of static form
+- one question per step
+- progressive disclosure: ask only the next missing datum
+- birth-time uncertainty is accepted instead of forcing a fake exact time
+- profile-missing guidance instead of generic failure
+- 资料缺失时引导补全，不把缺失说成系统错误
+- mobile-first chat layout
+- starter questions after onboarding
+- visible evidence-status language: based on chart evidence, not generic horoscope prose
+
+## Research-safe abstraction
+
+Target form: research interaction prototype.
+
+Allowed:
+
+- onboarding flow contract
+- prompt/response transcript fixtures
+- birth-time uncertainty UX notes
+- evidence-status display notes
+- mobile layout references
+- tests that ensure missing data prompts are useful
+
+Forbidden:
+
+- 不迁移积分、支付、商业账户权益
+- no Supabase service-role runtime
+- no production authentication dependency
+- no commercial redemption/admin-code logic
+
+## Contract requirements
+
+1. If name is missing, ask for name/nickname only.
+2. If birth time is missing or uncertain, ask for known precision; do not force exact time.
+3. If place is missing, ask for place after birth-time step.
+4. If profile remains incomplete, explain the missing field and continue useful guidance where possible.
+5. When chart evidence is available, label answers as evidence-based.
+6. Do not hide claim boundaries behind a friendly UI.
+
+## Next implementation target
+
+Create a lightweight research prototype that can replay onboarding transcripts and show which evidence layers would become available after each step.
@@ -0,0 +1,58 @@
+# Cross-repo advantage sync status — 2026-07-19
+
+Scope: this window synchronizes strengths between the research repo and the commercial repo.
+
+## Direction rules
+
+### Research → Commercial
+
+Move mature astrology capability, validation contracts, oracle boundaries, and answer policies only.
+
+Already synced or in progress:
+
+- timing precision contract: `verified_window`, `candidate_windows`, `exact_triggers`, `claim_status=exploratory_unvalidated`
+- three-engine mismatch attribution
+- Xalen fourth-oracle formula isolation
+- VedAstro hosted/pinned identity boundaries
+- Shadbala/Ashtakavarga component provenance registry
+- gender interpretation boundary
+- day-level holdout validator/template/blind-eval/intake scaffolding
+
+Blocked / not upgraded:
+
+- day-level holdout: still awaiting independent human negative labels
+- VedAstro hosted identity: hosted deployment build/version still not pinned
+- Shadbala/AV worked example: lineage attribution exists, but authoritative step-by-step worked example arbitration is still incomplete
+
+### Commercial → Research
+
+Move user-experience knowledge that improves research interaction prototypes; not credits, billing, payment, or Supabase service-role runtime.
+
+Commercial UX strengths to abstract:
+
+- conversational onboarding
+- 称呼 → 出生时间 → 出生地点 → 时间校正
+- mobile-first chat layout
+- evidence-based answer status
+- profile-missing guidance instead of generic failure
+- starter question suggestions
+- birth-time uncertainty flow
+
+Research-safe target:
+
+- research interaction prototype
+- UX contract documents
+- testable prompt/flow expectations
+- no commercial account/credit/payment runtime
+
+## Next sequence
+
+1. Keep this ledger current after every cross-repo sync.
+2. Run the commercial eight-question astrology E2E acceptance contract.
+3. Abstract commercial onboarding UX back into research docs/prototypes.
+4. After DB/business dependencies are handled by collaborators, add a formal gender field chain if needed.
+5. Continue deep blockers: day-level holdout, VedAstro hosted identity, Shadbala/AV worked example.
+
+## Current claim boundary
+
+File sync is not equal to runtime proof. A capability is only `e2e_verified` after a real commercial question demonstrates the expected layers in answer context and the answer respects all boundary language.