Skip to content

Archetype card: the board's compact card and page top (A1–A23), from the #1006 canvas (D620) #1323

Description

@guillaumelauzier

S1: The rest of the owner's archetype canvas. Decision D620, no migration expected. Slot S01.

The owner's #1006 artifact (https://claude.ai/artifact/6yTsUgRHkkiCwBpfZpwshh) is committed by D619 as design/canvases/integrated/Studio · Archetype card.dc.html. D619 builds its A24–A30, the three sections under the card. The board's earlier artboards draw the compact /studio card and the top of /studio/archetype differently from what runs on main. #1006's prompt asked to keep the card's top as it was, so those boards are this task.

What the board draws, against main

A1–A4, A10 and A9: the compact card on /studio. On main this is ArchetypeCard in components/profile/ProfileFitSection.jsx, built to Studio · Archetype preview (S1–S15) by D325 and D594.

  • There is no "Preview" chip.

  • "View full card →" sits in a footer row under a hairline, with the illustration's setting on the right.

  • Hover adds a shadow to the 2px lift and the accent border that main already has. The focus ring's offset is 3px; main uses 2px.

  • A10, locked:

    • "Archetype card is part of the Studio plan.";
    • then "Primary archetype · Locked";
    • then "Your answers are kept; the reading unlocks with the plan."

    main shows D594's line, which names the plan.

  • A9, on a phone: a 96px sprite beside the copy, with the description left to the page. main draws S15's 180px sprite, stacked.

A5–A8, A8f and A11–A23: the top of /studio/archetype (pages/ArchetypeCardPage.jsx).

  • A crumb row at the top ("‹ Studio", "Profile & Fit · Archetype"). At the foot, "‹ Back to studio" and the slug.
  • In the banner:
    • the licence as a chip beside "Primary archetype";
    • a 32px title;
    • the tagline, with a confidence pill;
    • a 3px hairline in the archetype's colour.
  • Below the banner, a 7/5 layout:
    • on the left: Core approach, Description, then Strengths and Blind spots;
    • on the right: three wells (Confidence as a figure and a bar; Complements as chips in each sibling's colour; "How we read this"), then the illustration's setting.
  • both resolves to the man's still. main splits the banner 50/50.

S1's recommendations (the owner can overrule them)

  1. Keep the split for both. An unset illustration also reads both, so resolving it to the man's still would show a man to every member who never chose.
  2. Keep the copy that later decisions set:
    • "with Eadwyn", never "the advisor" (D322);
    • a failed read that says what it does not claim, with a retry (D325);
    • D594's locked line, which names the plan.
  3. Keep the Level / XP bar (D325), which the board does not draw. It goes in the right-hand wells, under Confidence.
  4. The newer board wins for the compact card where A1–A10 and Studio · Archetype preview disagree. The older canvas stays committed as the record of D325 and D594.

Related: the card's archetype and the timeline's

  • The card reads GET /best-fit/me. Its archetype comes from the v1 classifier (loadLatestArchetype in services/archetypeScoring.ts).
  • The timeline (D619) reads the profile snapshots' displayed archetype, which is v2 and has hysteresis.
  • Where it was left. archetypeScoring.ts says v1 "keeps serving its callers until Session 15 moves the card page". D602 kept the card on best-fit/me.
  • When the two differ, D619's timeline says so, and does not mark a "Current" that contradicts the banner.

Moving the card to the v2 displayed archetype means the card's read must carry it, which is a Worker change. Decide it here, or split it into its own task.

Number. D620. If the build needs a migration, ask for its number on this issue.


Generated by Claude Code

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    slot:S01Work queue of slot S01state:readyReady for its slot to claim

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions