Understand remix lineage and recognition
Remix lineage credits the project that made an adaptation possible while keeping the new teacher’s version distinct.
Read lineage on a source project
Section titled “Read lineage on a source project”An eligible published project’s header shows how many published remixes it has received. The count reflects adaptations that completed publication, not every private draft someone started.
The source page continues to name its original teacher and school context. A remix carries that source project and teacher into its own Authoring and publication flow.
What credit does—and does not—mean
Section titled “What credit does—and does not—mean”Lineage records influence and makes related work traceable. It does not transfer ownership of the source, merge the two projects, or let a later source edit rewrite an existing remix.
The remixing teacher owns and is responsible for the adapted version. The source teacher remains visibly credited for the project it came from.
Recognition after publishing
Section titled “Recognition after publishing”Rectangle may show lightweight recognition when a teacher publishes a first project or when their work begins to travel through remixes. These moments acknowledge contribution; they do not change project permissions, visibility, or evaluation.
Profile and public-lineage details appear only when the source teacher’s visibility settings allow them. A missing public profile or lineage section should not be treated as proof that no relationship exists.