The snippets, ordered obscure → unmistakable

  1. Snippet 1(Generic helper)
  2. Snippet 2(Resource quantity)
  3. Snippet 3(API object)
  4. Snippet 4(Controller reconcile loop)
  5. Snippet 5(Scheduler predicates)
  6. Snippet 6(kubectl entrypoint)

Why this project gives itself away

The give-away. Snippets 1 and 2 are generic Go + a typed Quantity. Snippet 3 reveals `metav1.TypeMeta` / `ObjectMeta` + struct-tag-driven JSON — the Kubernetes API machinery. Snippet 4 names ReplicaSet + expectations.DeleteExpectations (the famous expectations cache). Snippet 5 is the scheduler plugin framework — framework.CycleState, UnschedulableAndUnresolvable. Snippet 6 is the kubectl main package with the Apache 2.0 + "The Kubernetes Authors" header.

How a Framed puzzle is built

Every Framed project ships exactly six snippets, hand-ordered from deeply obscure to unmistakable. The first snippet must be plausible for a dozen codebases — a generic loop, a small utility, a comment that could appear anywhere. The last snippet carries a project-specific tell: a function name, a code-comment idiom, a file header, a build invocation. Between them sit four snippets that gradually narrow the field. Reading them in order is half the puzzle: a returning Framed player learns to triangulate on indentation conventions, comment voice, naming, and the small-but-distinctive choices that betray a project's era and community.