Skip to content

Clarify Seedance real-person profile ID lifecycle - #16

Open
think-back wants to merge 1 commit into
mainfrom
docs/clarify-real-person-profile-id
Open

Clarify Seedance real-person profile ID lifecycle#16
think-back wants to merge 1 commit into
mainfrom
docs/clarify-real-person-profile-id

Conversation

@think-back

@think-back think-back commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • document that the returned rph_... ID is the stable client-facing identity and should be saved and reused
  • clarify that upstream real-person group identifiers are bound and managed internally after verification
  • document multi-profile recovery, same-profile verification retries, and local-upload storage fallback in English and Chinese

Validation

  • npx --yes mint@latest validate (pass)
  • git diff --check (pass)
  • npx --yes mint@latest broken-links reports 50 existing failures outside the two changed Seedance pages; neither changed page is listed

Document the client-facing profile ID lifecycle, internal upstream group binding, profile recovery, and upload-storage fallback in both language guides.

Constraint: Public API exposes rph_... while upstream group identifiers stay internal

Rejected: Adding external_person_id to the public API | The deployed strict request DTO accepts only name

Confidence: high

Scope-risk: narrow

Directive: Preserve one logical person per rph_... across verification retries

Tested: npx --yes mint@latest validate; git diff --check

Not-tested: Full repository broken-link check has 50 pre-existing failures outside the changed pages
@mintlify

mintlify Bot commented Aug 24, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
flatkey 🟡 Building Aug 24, 2026, 3:29 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant