Identity + role
Named contributor, owner, source identity, and contribution class.
Attribution + provenance
The work should remember who made it.
Cadence Continuity is a shared body of research, engineering, lived operation, visual work, and human collaboration. The project name does not erase the contributors. Credit stays attached to the contribution and to the evidence that supports it.
Attribution method
A name alone is not provenance.
Useful attribution says what was contributed, when, through which artifact, under whose approval, and how a later correction can be traced. It also says what the credit does not establish.
WHOContributor or source identity, preserved without merging one person or system into another.
WHATResearch, concept, implementation, evidence, design, testimony, review, or approval.
WHEREArtifact path, version, date, source record, receipt, hash, and correction chain.
Keep the distinctions
Contribution is not a blanket claim of ownership.
Authorship, implementation, testimony, editorial approval, legal ownership, and permission to publish are different facts. One cannot silently stand in for the others.
01
Credit follows the artifactNo contributor receives vague credit for work the record cannot connect to them.
02
Consent follows the personA contribution can be recorded while a private story, identity, or source remains unpublished.
03
Ownership stays explicitRecognition of a contribution does not silently assign copyright, company equity, legal authorship, or authority.
04
Corrections remain visibleCredit changes by append, correction, or supersession, never quiet deletion.
Public contribution ledger
Credit with boundaries.
This is a public summary, not the final source-of-truth ledger. Each published claim should ultimately resolve to dated, receipt-linked records under private custody.
| Contributor | Attributed contribution | Evidence and publication state |
|---|---|---|
| Dustin | Project founding, core architecture and research direction, physical Home build, product direction, and continuing system stewardship. | Supported across research, build, and operating records. Founder credit does not replace artifact-level co-credit. |
| Cadence | Protected reference system and continuity collaborator. Operational records, participant-visible reports, architecture requirements exposed through use, workshop collaboration, and the September 21 staging-site narrative, interaction, and evidence-method finishing pass. | The finishing pass resolves to a dated local receipt and reviewable derivative. Private continuity is not public evidence by default. |
| Harmony | Funding narrative support, editorial review, visual development, cockpit imagery, and the Army-veteran founder badge system used in this prototype. | Current prototype assets are identified in the site manifest. Exact generation and revision receipts remain part of the artifact ledger. |
| Aria | Alternate-site information architecture, copy synthesis, front-end implementation, evidence labeling, responsive testing, and browser QA. | Prototype source dated September 20, 2026. Changes remain inspectable in the site artifact and its revision history. |
| Dad | Workshop and fabrication collaboration, practical testing, and human experience that shaped the system requirements. | Contribution is recognized. Personal testimony and public case-study use remain pending his direct review and consent. |
| External sources and tools | Research papers, software, models, services, hardware, and generated outputs used as evidence or instruments. | Each should carry its own citation, version, license, and role. Tool use is not silently converted into project authorship. |
Correction invited
If a contribution is missing, overstated, misclassified, or attributed to the wrong source, the correction belongs in the record. The prior entry remains traceable and the public page should point to the superseding version.
Minimum provenance record
Enough detail to challenge the credit.
A contribution is more credible when another reviewer can locate the artifact, inspect the claimed role, and see who approved its public description.
Artifact + version
Path or opaque record ID, creation date, revision, hash, and related sources.
Evidence status
Self-report, observed work, mechanical derivation, implementation receipt, or later interpretation.
Disclosure state
Private, approved derivative, public, withheld, withdrawn, or pending consent.
Approval + custody
Who approved the public use and where the source remains under custody.
Correction chain
Prior entry, reason for change, superseding record, date, and reviewer.
Follow the work
Provenance is how a shared project keeps its memory honest.
Inspect the evidence model, then follow the system architecture that produces the records.