Skip to content

Audit: the public/private inventory — what lives in amicode vs amicissimo vs the fork #850

Description

@aarontrowbridge

Important

Problem — Aaron's ruling: "most things should be in amicode." After the fleet overlay landing and the fork retirement, nobody has walked the inventory: is anything premium-adjacent ungated in amicode? Is anything base-ish stranded in amicissimo? Is anything still living on the retiring fork that needs re-homing or an upstream ask?
Approach — Read-only audit, three lenses: (1) amicode — sweep for fleet/coordination-flavored surfaces staging WITHOUT the entitlement (the freeze validator governs the overlay→base direction; this checks base→world); (2) amicissimo — sweep for base-class content that belongs in the product (the strategy surface's serve-path is settled; what else lives there?); (3) the fork — what remains on the patch stack that the overlay or an upstream PR should absorb (the yellow-chunks UI work included). Output: an inventory table + disposition per row (move / gate / upstream-ask / retire), each disposition its own follow-up issue.

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

    hitlNeeds human decision or review

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions