Strategy statements — evidence

Approval update, 5 October 2026. Joe accepted all three displayed strategy recommendations. The recorded decisions supersede their pending status. The evidence below records bounded preparation. The wider strategy list, complete system audit and repairs remain open.

Recovered decisions and scope

Read the original July 20 R2-7 approval and July 19 card, the current strategy ruling, Content guidance, the original B-03 bundle and its current identity extraction. The entity/product architecture reference supplies an earlier strategy vocabulary, not approval of every definition or proof of current storage.

The approved distinction keeps source-documented strategy separate from derived analysis, with links to source, work and maker. Company and product positioning are already distinct. The new packet does not ask either capability again. The old brand-only wording is qualified because the subject of a statement and the piece supporting it are different relationships. Historical review cards retain their original wording as records.

Inspected primary text examples

• Inter IKEA culture and values: the source distinguishes Vision, Business Idea and values, while explaining vision through organizational purpose.
• Microsoft Code Book: the source introduces Mission through organizational purpose and separates values, culture and leadership material. This is the inspected publication, not a claim that every current Microsoft source uses identical wording.
• Red Hat brand platform: the public text names three platform statements and explains its promise. Detailed statements behind login were not accessed.
• NC State brand platform: the page uses Brand Promise to explain organizational purpose. Source names can overlap; they do not establish a universal alias map.

These examples were inspected as text. No animation, visual-treatment classification or inferred campaign membership is used. The recommendation preserves source terminology while supporting explicit comparative interpretation. A shared display can still hold several distinct meanings.

Selected system and consumer evidence

strategy-boundaries-preflight.json preserves literal read-only schema and selected-shape queries, seven hashed local excerpts and the exact historical approval reference. The queries show selected strategy metadata and guideline sections; they do not prove source truth, completeness or deployed writer identity. Missing named fields do not exclude equivalent information in other JSON or tables.

The inspected local onboarding prompt requests mission, positioning and values. Its user prompt can instruct generation from training knowledge when extracted source text is absent. The seed path writes guideline sections unpublished and merges generated metadata. The consumer page prefers available sections, then can derive sections from metadata. The mission adapter titles its output Mission & Vision even though the selected input is mission alone.

These are specific compatibility and evidence concerns, not proof of a production failure. The complete audit must test actual route activation, permissions, validation, source links, publication and reanalysis. It must establish whether human corrections survive replacement or metadata merging and whether unpublished generated descriptions can reach a display by another path. No code or record was changed to resolve those questions here.

Human meaning through the workflow

Capture must retain the relevant source and passage. Interpretation needs its own identity rather than becoming a quotation. The subject may be a company, a product or a supported campaign context; the publisher and credited strategist can be different parties. Several sources can support one claim, and one source can support several claims. No blanket inheritance follows.

Before implementation, trace extraction into validation, writes, publication and every reader. Compare source-named and interpreted search results; preserve that distinction in tracker rules and Ask citations. Changed or withdrawn sources must not silently rewrite the evidence behind an earlier conversation. Monitoring, scheduling, permissions and costs remain part of the full audit.

Physical keys, constraints, relationship direction, multiplicity, junctions, indexes, query plans and repair/rollback contracts remain unverified here. The meaning review can advance without pretending those engineering checks are finished. Retaining one prose description, imposing one required hierarchy and selectively preserving source distinctions were compared; the packet recommends the last approach.

Prepared 5 October 2026.

Earlier reconciliation, before the later verbal and strategy reply

The current choices and linked primary text examples were checked again against the latest recorded decisions. Searchable calls to action, price, benefit and terms are already approved across media. That does not answer the proposed Brand Promise versus Value Proposition boundary or the other two strategy choices. Those three remain pending; no question was resent.

The selected system evidence above remains dated evidence. This consistency pass did not rerun its database queries or establish deployed behavior. It changes the review boundary, not the physical model, prompt or publication rules. Source terminology and analyst interpretation must remain distinguishable when implementing the final decisions.

Later approval recorded

The exact reply is preserved in docs/reference/2026-10/2026-10-05/verbal-strategy-joe-response.txt, with six separate mappings in verbal-strategy-joe-answers.json. It approves the six displayed recommendations only. The earlier pending statements above describe the checkpoint before that reply. The original bundle remains partial, and no storage, prompt, schedule or runtime change follows from recording these answers.