[codex] document character onboarding and platform next steps - #144
Draft
meekmachine wants to merge 3 commits into
Draft
[codex] document character onboarding and platform next steps#144meekmachine wants to merge 3 commits into
meekmachine wants to merge 3 commits into
Conversation
meekmachine
force-pushed
the
codex/document-inspection-preflight
branch
from
May 28, 2026 03:22
df5c2b4 to
d2e5ccf
Compare
Owner
Author
Full triage — REWORK before mergeKeep Embody onboarding/preflight docs; drop Latticework/agency framing. SoM/agencySociety → Polymer/LoomLarge. |
Owner
Author
PR backlog triage — DRAFT_KEEP / REWORKDrop Latticework/agency framing before merge; Embody onboarding docs OK. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
extractFromGLTF,collectMorphMeshes,suggestBestPreset,generateMappingCorrections,validateMappingConfig,validateMappings, andanalyzeModelworking togetherMappingConsistencyResult,ModelData,ValidationResult, correction results, preset compatibility, and best-preset selectionVISION_AND_PRD.md, connecting recent Loom3, LoomLarge, and Polyester/Latticework progress to the larger character-platform directionWhy
The original update documented helper methods but did not explain the larger user workflow. These APIs matter because they let Loom3 and LoomLarge turn unknown character asset internals into a validated semantic profile. Once that profile exists, users and AI-driven workflows can control a character through expressive intent, such as AUs, visemes, gaze, head movement, emotes, poses, authored morphs, and expression clips, instead of manually wiring rig-specific morph and bone names.
The vision update also captures what the recent project work is teaching us: profiles are the product contract; preflight is the start of character rigging; AI authoring needs previewable, structured, minimal patches; and runtime portability should be extracted in vertical slices around proven workflows.
Validation
origin/mainafter Loom3 PR Harden runtime morph authoring #160git diff --check origin/main...HEAD