# Value Attribution Data Architecture: Action Items

Source: whitepaper by Shawn, v0.1.5 (Doc dated November 5, 2026), latest revision pulled from Drive on November 4, 2026, 7:20 PM PT. Build source is the Doc's HTML export (it keeps Roboto Mono code formatting and nested list styles that the Markdown export drops); embedded images come from the Markdown export, but the page loads the media-library files in the image map. Status: rendered as a TF Project (te_page Custom HTML block, same pattern as Prompt Caching); content verbatim pending review by a separate group; schema tables open for UX review. Updated November 4, 2026.

## On hold: Shared Project for HTML builds

Paused on November 4, 2026, while the Doc is brought to a reviewable state. Resume once the fixes land: rebuild the page from the reviewable revision, then set up the Shared Project and its assets.

- **Shared Project:** the knowledge. Custom instructions (no content changes, always verify, deliver CMS block plus preview, check rulings first) and five docs: build rules, layout rulings log, deployment checklist, reference example (Prompt Caching block), and a page record per Paper (this doc moves there).
- **Skill:** the machinery. Packaged cleanup (Drive HTML export), build, and verification scripts. Move layout rulings, the image map, and the dataset color map out of the build code into a per-page settings file (plain lists, colors, image names and alt text, hero label) so the owner can add rulings by prompt.
- **Before handoff:** confirm the owner's WordPress role can post unfiltered HTML (needed for the Contents script and scoped styles), name one owner for the rules and rulings docs, and publish to staging before going live.

## Image map (current)

All in /wp-content/uploads/2026/11/. Use these names on every rebuild.

| Section | File | Alt text |
|---|---|---|
| 1. Conceptual Overview | value-attribution-five-datasets-v2.png | Five datasets in the value attribution chain: Cost and Usage (metered bill), Telemetry (runtime activity), Tasks (deliverable), Outcomes (verified result), and Value (realized worth). |
| 1.3 Execution Hierarchy | value-attribution-execution-hierarchy.png | Unchanged. |
| 2.1 Logical Overview | value-attribution-schema-join-chain-v2.png | Updated November 4, 2026. Alt text unchanged; confirm it still matches v2 (the Doc still embeds the old image, so v2 has not been reviewed here). |

## Standing layout rulings

Apply to every rebuild. Content stays verbatim to the Doc.

- **Plain lists (no card or design treatment):**
  - Section 1 dataset list (the five questions under the first figure), ordered. November 4, 2026.
  - Section 5 roadmap list, unordered. November 4, 2026.
  - All lists in 2.4 Scrap, Friction, and Rework, which stay plain as previously approved even though the Doc bolds their labels. November 4, 2026.
- **Nested ordered lists are lettered** (a., b., c.) everywhere, per the owner, even where the Doc's export reports roman numerals (2.4.2, 2.4.3). Enforced with a scoped class (va-alpha) so theme list styles and attribute stripping cannot revert it. Nesting follows the Doc's indent levels. November 4, 2026.
- **Code formatting follows the Doc.** Text set in Roboto Mono or Courier renders as code, including inside headings (for example, the 2.5 subsection headings). Bold plus mono keeps both. November 4, 2026.
- **Section links.** Every "Section N" mention in body text links to that heading's anchor, including ranges such as "Sections 2 through 4." November 4, 2026.
- **Trailing colons.** Removed from card titles, headings, and Contents labels in the Project output; they stay in the Doc, and prose keeps its punctuation. November 4, 2026.
- **Table naming column.** Gets a minimum width (9.5rem) so short names stay on one line; column-name code never wraps; longer names and descriptive cells may wrap. Long identifiers in later columns break at dots and underscores. Tables too wide for the screen scroll inside their frame. November 4, 2026 (revised from "never wrap").
- **KPI tables (Section 4).** One locked layout for all four tables: KPI Name 22 percent, Formula / Derivation 40 percent, Strategic Purpose 38 percent. November 4, 2026.
- **Footer version line** reads the version and date from the Doc's "Version" line. November 4, 2026.
- **Dataset colors (round 1, pending owner review).** One hue per dataset, drawn from the diagram icons: Cost and Usage sky #38bdf8, Telemetry amber #f5a524, Task violet #a78bfa, Outcome green #34d399, Value lime #d4ef3d; Workload uses the brand blue #4f7cff. Span and Trace take Telemetry's color because they aggregate into it. Applied as:
  - a top bar on cards in 1.1, 1.3, and 2.1 (join cards blend both datasets' colors);
  - a colored marker, table rule, and column-name tint on schema subsections 3.1–3.5;
  - a blended bar under KPI headings 4.1–4.4 showing which datasets each KPI set uses.
  Plain lists get no color.

## Open decisions

1. **Shape.** Current render: one Project page with the schema tables inline and open. Earlier recommendation, pending UX review: move Section 3's schema to a versioned TF docs reference page. Optional: an Insights article (about 1,200 words) from Section 1 for launch.
2. **Editorial gear.** Medium pass recommended once the content review closes; Light if the reviewing group treats the draft as near-final.
3. **Framing and title.** Publish as a "v0.1 draft for comment" inviting pilots, or as a finished Paper? Keep the current title?
4. **Byline.** How to credit the author and contributors. The footer holds a TODO for license and acknowledgments.

## Doc items for the owner

- [ ] **Column names in 2.5 prose are not in Roboto Mono in the Doc** (for example, RealizedValue, StakeholderRoleName, OutcomeId, AttestorId, AttestedDateTime). The headings and some mentions are. Set them in the Doc if they should render as code.
- [x] **Duplicate H4 numbers** fixed in the Doc (2.1.1–2.1.3). November 4, 2026.

## UX review of the Project render

- [ ] **Dataset colors:** owner to review round 1. Options for round 2: color the Contents rail numbers for 3.1–3.5, add semantic colors (warning, critical) for scrap and UNLINKED concepts in 2.4, or tint the Section 2.1 summary table rows.
- [ ] **Hero eyebrow** reads "Tokenomics Foundation" (layout addition). Confirm or replace (for example, a series or working group label).
- [ ] **Cards:** remaining card lists are in 1.1, 1.3, 1.3.1, 2.1 (datasets and joins), and 2.2.2. Confirm which should also stay plain lists.
- [ ] **Schema tables (3.1–3.5)** are open, not collapsed. Tables scroll sideways on phones; none overflow on desktop.
- [ ] **Contents rail** lists H2s and H3s (23 links). Consider H2s only.
- [ ] **Schema diagram** is unreadable at phone width. Consider tap-to-enlarge or a link to the full-size image.

## Diagrams and links

- [ ] **Schema diagram v2:** confirm its labels now match the tables (v1 showed BaselineTaskCount and BaselineOutcomeCount, AttestorName, ValueAttestedDateTime, and OutcomePeriodStart/End on Value). Update the alt text if the labels changed.
- [ ] **Upload images** per the image map above.
- [x] **Section 1 diagram updated** to v2. November 4, 2026.
- [x] **Schema diagram updated** to v2. November 4, 2026.
- [x] **Companion documents and version history:** the author marked this header section "not meant to be loaded onto the website"; it is omitted from the render.
- [x] **Design brief links:** the Doc refers to "a forthcoming design brief" and drops the "See the Design Brief" sentences.

## Schema consistency (as of the 7:20 PM pull)

- [ ] **"Consumption Scope" is never defined as a column list**, though it is the cost-to-telemetry join key. A drafting note also remains in 2.1.2: "The definition of the grain needs further discussion in the FOCUS WG."
- [ ] **Telemetry.ModelId** still joins to SkuPriceDetails.ModelId, which the CostAndUsage table does not list. Naming also alternates between "Cost and Usage.X" and "CostAndUsage.X."
- [ ] **Telemetry row grain** (2.1 text) omits WorkloadId, which the grain table includes. Recheck.
- [x] **Task table spacing:** "Task Rework Penalty Quantity" fixed.
- [x] **Outcome.WorkloadName** no longer refers to a Task.WorkloadName column.

## KPIs (Section 4)

- [x] **Intro** now describes four layers, matching the four subsections.
- [x] **Scrap-Adjusted Margin Erosion** description no longer includes post-delivery SLA rollbacks.

## Governance, neutrality, and claims

- [ ] **FOCUS stewardship:** confirm the Linux Foundation and FinOps Foundation references are consistent. House style also calls FOCUS a specification, not a standard.
- [ ] **Forward-looking commitments need FOCUS WG and TF sign-off:** "The FOCUS Working Group shall partner with the OTel SemConv SIG," FOCUS 1.6 timing, the June 2027 playbook, and the June 2027 conference demo.
- [ ] **Vendor neutrality:** many named products across Sections 1.2, 2.2, and 2.2.2. Consider keeping them in the Section 1.2 table only and using categories in prose.
- [ ] **Figures to source or label illustrative:** "~99%" row-volume reduction (Section 3.2) and "3x–5x" output-token weighting (Section 2.3).

## Style (for the editorial pass, not applied yet)

- [x] Em dashes removed in the Doc.
- [x] "This article" now reads "paper."
- [ ] "->" arrows in prose; "vs." usage; "&" in headings.