{
 "updated_pst": "2026-11-03 7:50 AM PST",
 "note": "Append entries here; each needs ts_pst, section (Technical, Compliance, Capacity, Timing, Tradeoffs, Next validation, AI decisions), type, entry, ref, status. Earlier entries are never edited or removed; add a new entry that supersedes one.",
 "entries": [
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Technical",
   "type": "constraint",
   "entry": "Reliable connectors exist only for the case system and document repository; ticketing, call-recording and policy systems each need a new connector and security review.",
   "ref": "E09",
   "status": "active",
   "id": "C01"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Technical",
   "type": "constraint",
   "entry": "Deployment has on-prem model endpoints, role groups, append-only audit storage and source-system permission checks; no field-level redaction across sources.",
   "ref": "E14",
   "status": "active",
   "id": "C02"
  },
  {
   "ts_pst": "2026-11-03 7:14 AM PST",
   "section": "Technical",
   "type": "decision",
   "entry": "Architecture follows Kamiwaza's secure, decentralized Inference Mesh: data stays where it lives, inference runs locally, no central copy of source data. Direction from S at 7:14 AM PST (8:44 PM IST).",
   "ref": "S, Nov 3; kamiwaza.com/inference-mesh (verified page read); CS1",
   "status": "decided (S)",
   "id": "C03"
  },
  {
   "ts_pst": "2026-11-03 7:05 AM PST",
   "section": "Technical",
   "type": "decision",
   "entry": "Client environment mapped onto Kamiwaza's product architecture (Distributed Data Engine, Inference Mesh, Retrieval Service, ReBAC authorization, Activity Logging and Audit, Model Management, Connector Framework). Direction from S at 7:05 AM PST (8:35 PM IST).",
   "ref": "S, Nov 3; kamiwaza.com/product (verified page read)",
   "status": "decided (S)",
   "id": "C04"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Technical",
   "type": "assumption",
   "entry": "Packets store references (source IDs, versions, passage locations), not copies; passages are read in place under the viewer's permissions.",
   "ref": "A18; CS1; E07; E11",
   "status": "assumption - validate week 1",
   "id": "C05"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Technical",
   "type": "assumption",
   "entry": "Northstar's deployment includes the Kamiwaza components the plan uses; the case lists only E14's components.",
   "ref": "A19; CS1; E14",
   "status": "assumption - validate week 1",
   "id": "C06"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Technical",
   "type": "assumption",
   "entry": "Role groups and source-system permission checks can be enforced through Kamiwaza's ReBAC authorization.",
   "ref": "A17; E07; E14; kamiwaza.com/product",
   "status": "assumption - validate week 1",
   "id": "C07"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Compliance",
   "type": "constraint",
   "entry": "Every material claim links to an authorized source; audit record keeps approver, source set, model and prompt version, edits and final disposition.",
   "ref": "E06",
   "status": "active",
   "id": "C08"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Compliance",
   "type": "constraint",
   "entry": "Automated dispositions are not approved; a human records every disposition.",
   "ref": "E06; Scenario ¶2",
   "status": "active",
   "id": "C09"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Compliance",
   "type": "constraint",
   "entry": "No user sees or retrieves a source they cannot access in the underlying system; exports never reveal restricted content.",
   "ref": "E07",
   "status": "active",
   "id": "C10"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Compliance",
   "type": "decision",
   "entry": "Exports withhold restricted sources entirely, because field-level redaction does not exist.",
   "ref": "E07; E14; A5",
   "status": "proposal",
   "id": "C11"
  },
  {
   "ts_pst": "2026-11-03 7:09 AM PST",
   "section": "Compliance",
   "type": "principle",
   "entry": "AI work is never silently overwritten: every assumption, claim, decision, prompt and command is logged and versioned, a human approves any change, and the original is kept in the audit trail.",
   "ref": "E06; E11; E13; E14; Kamiwaza Activity Logging and Audit (kamiwaza.com/product, verified)",
   "status": "active (S)",
   "id": "C12"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Capacity",
   "type": "constraint",
   "entry": "Two engineers and one product designer for the first four weeks; one engineer moves to another commitment after week 4.",
   "ref": "Scenario ¶4; E09",
   "status": "active",
   "id": "C13"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Capacity",
   "type": "assumption",
   "entry": "Designer time after week 4 is not available; weeks 5-6 are hardening and rollout only.",
   "ref": "A7; E09",
   "status": "assumption",
   "id": "C14"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Capacity",
   "type": "constraint",
   "entry": "Broader integrations, model training and new identity infrastructure are unavailable in the window.",
   "ref": "Scenario ¶4",
   "status": "active",
   "id": "C15"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Timing",
   "type": "constraint",
   "entry": "Credible first release in six weeks; executive demo at six weeks (treated as one milestone).",
   "ref": "Scenario ¶4; E08; A6",
   "status": "active",
   "id": "C16"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Timing",
   "type": "constraint",
   "entry": "Renewal decision in ten weeks.",
   "ref": "E12",
   "status": "active",
   "id": "C17"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Timing",
   "type": "open",
   "entry": "Calendar dates are not in the PDFs (fictional case date); plan uses W1-W10. Exercise submission deadline: per invitation, confirm.",
   "ref": "E14; Instructions: upload; N7",
   "status": "open",
   "id": "C18"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Tradeoffs",
   "type": "decision",
   "entry": "First release limited to two connected sources; the other three lead the roadmap.",
   "ref": "E09; E12; E05",
   "status": "proposal",
   "id": "C19"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Tradeoffs",
   "type": "decision",
   "entry": "CTO demo shows the governed two-source workflow, adoption numbers and a dated connector roadmap, not five systems, autonomous research, automatic disposition or a configurable dashboard.",
   "ref": "E08; E06; E09; E12",
   "status": "proposal",
   "id": "C20"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Tradeoffs",
   "type": "decision",
   "entry": "Kaizen autonomous actions and Tool Shed actions are out of the first release.",
   "ref": "E06; E08; kamiwaza.com/product",
   "status": "proposal",
   "id": "C21"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Next validation",
   "type": "open",
   "entry": "Sample recent cases to see how much evidence lives in each of the five systems.",
   "ref": "A1; E09",
   "status": "open - week 1",
   "id": "C22"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Next validation",
   "type": "open",
   "entry": "Interview pilot users who stopped using the draft summary.",
   "ref": "A2; E02",
   "status": "open - week 1",
   "id": "C23"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Next validation",
   "type": "open",
   "entry": "Confirm with compliance what counts as a material claim and which audit fields are required.",
   "ref": "A12; E06",
   "status": "open - week 1",
   "id": "C24"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "Next validation",
   "type": "open",
   "entry": "Test the permission re-check with a revoked document, as in the incident.",
   "ref": "A4; E11",
   "status": "open - weeks 2-3",
   "id": "C25"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "AI decisions",
   "type": "log",
   "entry": "Tab (AI) drafted the PRD, client environment, user stories, mind map, materials, release plan and this log from the four PDFs and the Kamiwaza research. Every item is pending S's review; nothing here is final until S approves it.",
   "ref": "Instructions: AI use",
   "status": "pending S review",
   "id": "C26"
  },
  {
   "ts_pst": "2026-11-03 7:20 AM PST",
   "section": "AI decisions",
   "type": "log",
   "entry": "Draft brief kept under 1,000 words (980 at this version) so S's own AI working notes fit.",
   "ref": "Instructions: what to submit; Brief template",
   "status": "pending S review",
   "id": "C27"
  },
  {
   "ts_pst": "2026-11-03 7:01 AM PST",
   "section": "AI decisions",
   "type": "log",
   "entry": "Low-fi frames are described on this site; the Whimsical mockups are being made separately and the link appears in the top bar when ready.",
   "ref": "S, Nov 3 (7:01 AM PST)",
   "status": "in progress",
   "id": "C28"
  },
  {
   "ts_pst": "2026-11-03 6:45 AM PST",
   "section": "AI decisions",
   "type": "change",
   "entry": "v1: tracker with PDFs word for word, checklist, Q&A, research.",
   "ref": "-",
   "status": "done",
   "id": "C29"
  },
  {
   "ts_pst": "2026-11-03 7:15 AM PST",
   "section": "AI decisions",
   "type": "change",
   "entry": "v2: tabs added (PRD, client environment, evidence to stories, mind map, materials, release plan).",
   "ref": "S email 6:59 AM PST",
   "status": "done",
   "id": "C30"
  },
  {
   "ts_pst": "2026-11-03 7:20 AM PST",
   "section": "AI decisions",
   "type": "change",
   "entry": "v3: Kamiwaza architecture, Constraints log, Presentation tab, Mockups link, brief loaded from its own file, AI change-control principle.",
   "ref": "S, 7:01-7:14 AM PST",
   "status": "done",
   "id": "C31"
  },
  {
   "ts_pst": "2026-11-03 7:22 AM PST",
   "section": "Compliance",
   "type": "rule",
   "entry": "S's RULE, Release 1: humans record the final disposition, always a priority. Even in automatic disposition the interactions are layered with humans and it is never fully 100% automatic, to mitigate risk and catch issues at the right time. In PRD (Considered), Release 1 and W1-W4; never out of scope or later. S's words: \"this should be in release 1 - Humans record final disposition is always a priority. Even in automatic disposition, the interactions are layers with humans and it is never fully 100% automatic, as it will increase the turn around time to mitigate risk or catch on right time. This is a RULE\"",
   "ref": "E06; S's rule (S email 8:52 PM IST / 7:22 AM PST)",
   "status": "in force",
   "id": "C32"
  },
  {
   "ts_pst": "2026-11-03 7:30 AM PST",
   "section": "AI decisions",
   "type": "change",
   "entry": "v4: Prototype link in the top bar, Presenter prep tab, S's rule (C32) added to PRD, release plan and mind map; out-of-scope rows reworded to \"fully automatic disposition with no human layer\" so the rule never reads as out of scope.",
   "ref": "E06; S's rule",
   "status": "done",
   "id": "C33"
  },
  {
   "ts_pst": "2026-11-03 7:40 AM PST",
   "section": "Compliance",
   "type": "rule",
   "entry": "S clarified 9:10 PM Nov 3: never fully automatic in any release; human governance in multiple layers; shown in red as a RULE. Supersedes the out-of-scope wording in C33: \"fully automatic disposition with no human layer\" is removed from every out-of-scope / not-doing list (PRD v1, PRD v2, release plan, mind map, brief, presenter prep), because it is a permanent product rule, not a scope item. Red RULE banner added at the top of PRD v2, PRD v1, Constraints and Release plan; release plan states every release (R0-R3) keeps human checkpoint layers and none removes them. CTO ask (E08) rows kept, marked \"(conflicts with RULE; not planned)\". S's words: \"This is not out of scope right? Even in future releases it is never fully automatic, it should be governed by humans in multiple layers. Highlight this in red as a RULE\"",
   "ref": "E06; S's RULE (S email 9:10 PM IST / 7:40 AM PST); supersedes C33 wording; builds on C32",
   "status": "in force",
   "id": "C34"
  }
 ]
}