Centaur7 owns portfolio meaning: which projects appear, how their maturity is described,
when their evidence was reviewed, and which facts support each case study. It does not
own football valuation, fantasy scoring, league identity, or component behavior.
Those product meanings remain in the flagship repository that computes or enforces them.
Centaur7 reports committed evidence; it never becomes a second scoring engine, rules
registry, or component catalog.
Meaning Flows in One Direction
A flagship repository owns product rules and release evidence.
ProjectCatalog records the portfolio interpretation and inspected revision.
Project cards, briefs, case studies, and this guide consume that record.
ProfessionalProfile owns the public role titles, dates, and descriptions used by About and the portfolio PDF. Application resumes are dated editorial snapshots.
BittingInventory separately measures the exact package Centaur7 compiles against.
Current Professional Role:
Director of Client Experience and Product Design at Unlocked Data · June 2024 to Present
Load-bearing assumption: evidence crosses repositories through a deliberate
human review. The freshness test exposes neglected records; it cannot decide what a commit
means or whether candidate work has shipped.
Studio Identity and Biography
ProfessionalProfile owns
the role titles, dates, and descriptions used by About and the portfolio. Home and About
supply their editorial introductions. These are reviewed facts; the site does not infer
qualifications or outcomes from project activity.
Offline portfolio evidence links use public addresses. The deck owns slide IDs, titles, order,
and bookmark inclusion. The renderer derives page numbers from that order; the PDF assembler
resolves index links and bookmarks to native destinations in each edition. PageFragments owns route/query-preserving links and the safe focus selector for app-owned fragment IDs. Interactive startup retains that destination. PageMetadata uses the serving origin
for route canonicals, and the static renderer receives that origin at deployment.
PortfolioDashboardData owns the PDF dashboard’s fixed illustrative revenue values,
totals, ranked markets, and number formats. The map, chart, table, and compact summaries consume
that same record. Bitting owns geography, quantile boundaries, and legend labels; the print
composition selects three bands and declares the units. This specimen contains no client data.
Project Record
Meaning and Owner
One Project is Centaur7’s complete public brief for one flagship project.
ProjectCatalog.cs owns its identity, status, review date,
direction, links, KPIs, inspected revision, evidence scope, and decision trace.
Its Summary explains what the product does in overviews and brief openings; its Tagline preserves the project's
established positioning in the portfolio. Review dates and release evidence
remain here rather than competing with that overview.
Its ConceptIdentity keeps the project name and canonical logo together. The logo's SVG viewBox owns
its painted-artwork alignment; consumers use that asset rather than adding local offsets.
StudioDestinations owns the About/portrait and Colophon/publication-symbol pairings;
ConceptLabel and ConceptVisual render those identities across navigation and actions.
Boundary Example
“Six Fresh Bakes calls” is a portfolio fact. How those calls score is not: The
Weekly Dollop’s versioned scoring definition owns that rule.
Reach and Regression Evidence
ProjectCard, CaseStudyLayout, and this guide consume the
record. Catalog and case-study tests fail when required evidence disappears or a
consumer stops rendering it.
Scope: Merged Credit v5 / Archetype v4 source and rebuilt products, current careers and prospect navigation, and live Weekly Fantasy. Production Ivy method stamps and Yale crest versions were spot-checked on October 20. The provider-dependent admission/storage candidate in draft PR #225 remains excluded.
Current interpretation: Running Credit v5 and Archetype v4 on refreshed 2026 data, with career history, prospect navigation, and locked fantasy picks carried through updates.
Decision verification: The accepted twelve-conference migration and historical-admission, career, and fantasy checks passed release Quality run 39158088949; navigation follow-up run 39166677592 also passed. Production method and crest stamps were independently read on October 20.
Inspected evidence: TheWeeklyDollop origin/main e3c637333d4a (reviewed October 20, 2026)
Scope: The 2026 three game modes, shared league seats, replacements, season points and honours, public Sunday board, publication-gated Second Serving figures, and shared route openings. The published Bread Week issue and Dessert Week opening schedule were checked publicly; private league journeys were reviewed in source and existing CI, without accessing accounts or submitting picks.
Current interpretation: Publishing the 2026 Sunday paper and running public Fresh Bakes and private leagues, with shared team seats, Roll Model replacements, season points charts, and weekly honours.
Decision verification: Merged server contracts cover seat submissions, historical scoring, replacements, and league-note access. Publication-boundary checks cover Second Serving; current-main Competition quality run 39446961619 passed.
Scope: Inventory and charts measure the exact ci.73 package, published by successful run 39447103176 from source 882ba4d. Package-owned disclosures are used here. Dashboard print completion, pager/comparison improvements, and the sibling’s tooltip-click fix remain separately scoped sibling work; they are not claimed as shipped in this public package.
Current interpretation: Shipping shared page/grid composition, native supporting disclosures, persistent search labels, and reusable slide/tile layouts in the package consumed by this site.
Decision verification: Reflection tests measure the pinned package itself, while Bitting's consumer checks exercise both hosting models and narrow chart layouts.
Project Status Is an Evidence Claim
A status describes the strongest maturity claim the inspected evidence supports. It is
selected during review, not calculated from commit count, age, or marketing language.
Exploring
The problem and audience are still being tested.
Required evidence: A written product hypothesis and a named next decision.
Building
A coherent first release is under construction.
Required evidence: Working product code with a bounded release milestone.
Expanding
The core product works and is gaining a larger usable surface.
Required evidence: A working core flow plus shipped or candidate expansion work.
Live
People can use the current product at its public address.
Required evidence: A production URL and a verified core flow.
Maintained
The product is stable and receives deliberate improvements.
Required evidence: A usable release plus current maintenance or compatibility evidence.
Archived
The work is preserved but no active milestone is promised.
Required evidence: A retained artifact and an explicit end to active development.
Boundary case: shipped work can expand while its project remains
Live; a status changes only when the evidence supports a different maturity claim.
A later review may move a project in either direction.
Evidence Review Date
LastUpdated is the date Centaur7 checked the portfolio record against committed
project evidence. It does not claim that every inspected commit deployed that day.
The catalog test rejects an active record more than sixty days older than the newest review.
That detects neglect, not truth: the reviewer must still separate shipped, candidate, and
planned work and record the inspected revision.
Bitting Package Inventory
BittingInventory.cs owns claims about the exact
0.1.0-ci.73 package consumed here: 99
public components across 24 families. It does not describe
unreleased Bitting source work.
Boundary case: a component merged after 0.1.0-ci.73
remains source evidence, not a package count. Reflection tests compare this inventory with
the referenced assembly, so a package upgrade cannot silently leave the case-study figures behind.
Its Presentation slot owns metric labels and invariant count, average, and signed-difference formats. KPIs, chart axes and series, tables, and the Style Guide fact specimen consume that same metadata.
The owner also supplies the grouped remainder, package-wide parameters per component, and
the eight families furthest from that average. The ratio divides total parameters by total components;
averaging the family averages would give small families the same weight as large ones.
Distances are rounded once to one decimal using .NET’s nearest-even rule. The chart never sums those ratios into an Other bar.
Inputs are the nonempty public families in the pinned assembly. A zero-component family is outside
this inventory’s contract. Release counts describe their recorded release; upgrading today does not rewrite those historical points.
Independent expected outcomes and current production results
Example
Expected
Current
Grouped remainder 99 components; the named families contain 20, 14, 8, and 8.
49
49
Package parameters per component 971 parameters across 99 components; families have unequal sizes.
9.80808081
9.80808081
Fractional family average A two-component family declaring five parameters.
2.5
2.5
Rounded distance from the package Charts declares 289 parameters across 20 components.
4.6
4.6
Scope: Bitting 0.1.0-ci.73, source 882ba4d, reviewed October 20, 2026.
This is executable local evidence. It does not verify deployment or establish a flagship project’s rules.
Change the Owner, Then Prove the Reach
Public Professional Role
Owner:
ProfessionalProfile
Consumers to inspect:
About, PDF professional experience, this guide
Evidence:
Rendering and PDF export checks
Identity, Maturity, Direction, or KPI
Owner:
ProjectCatalog
Consumers to inspect:
Home card, project brief, case study, PDF identity, this guide
Evidence:
Catalog and rendering tests
Bitting Release or Counts
Owner:
BittingInventory
Consumers to inspect:
Bitting charts, KPI, package narrative
Evidence:
Assembly reflection tests
Football or Fantasy Rule
Owner:
Flagship repository
Consumers to inspect:
Its UI, API, artifacts, jobs, and Centaur7 summary
Evidence:
Flagship contract fixtures first; portfolio review second
Inspect the committed owner and record the exact revision and scope.
Separate shipped, candidate, and planned work before changing the portfolio claim.
Update the authoritative Centaur7 record once; do not restate its facts in consumers.
Run catalog, case-study, route, accessibility, and package-inventory checks, then regenerate the production HTML and portfolio.
Record unverified deployment or user evidence instead of converting uncertainty into a pass.
Reconsideration trigger: automate evidence transfer only when repeated manual
review causes a real stale or contradictory claim. Until then, a human interpretation is
smaller and more honest than cross-repository synchronization machinery.
The portfolio encountered a problem. Reload the page to try again.