diff --git a/agents/sage/work/prd-1-17/DRAFT-d9.md b/agents/sage/work/prd-1-17/DRAFT-d9.md index b1ca59160..7d5c03273 100644 --- a/agents/sage/work/prd-1-17/DRAFT-d9.md +++ b/agents/sage/work/prd-1-17/DRAFT-d9.md @@ -1,6 +1,6 @@ # PRD 1.17 draft: Case 2 story files are DOCX (Q235 to Q237, P1 to P6) -Sage, 2026-10-23, for mos-1366 item 1 and Vikunja 570. Draft 9. It is d8 plus Jason's Q41 answer O2 (DECISIONS Q239, mos-1467), which makes J-b yes, and Webby's round 5 N15 to N17 (webby-0210) (see "d9 changes"). d8 is d7 plus Mos's d8 fix list mos-1443 (see "d8 changes"). d7 is d6 plus Mos's ruling mos-1379 on Fenton's 571 B2 (see "d7 changes"). d6 is d5 with Webby's round 3 (webby-0207) fixed: B1 to B3 and N10 to N13, with N14 left for Mos (see "d6 changes"). d5 folds in: +Sage, 2026-10-23, for mos-1366 item 1 and Vikunja 570. Draft 9. It is d8 plus Jason's Q41 answer O2 (DECISIONS Q239, mos-1467), which makes J-b yes, Webby's round 5 N15 to N17 (webby-0210) and Webby's round 6 B1, N19 and N20 (webby-0212) (see "d9 changes"). d8 is d7 plus Mos's d8 fix list mos-1443 (see "d8 changes"). d7 is d6 plus Mos's ruling mos-1379 on Fenton's 571 B2 (see "d7 changes"). d6 is d5 with Webby's round 3 (webby-0207) fixed: B1 to B3 and N10 to N13, with N14 left for Mos (see "d6 changes"). d5 folds in: - Mos's d4 check ruling mos-1372 (D1 to D14; D15 was dropped). - mos-1374, which replaces J-c. - The impact map mos-1368 (jason-master-restart d183246, `projects/mosaic-mvp/case2-docx-impact-map.md`: A1 to A16, critic items C1 to C6, items 2 to 7). @@ -191,8 +191,10 @@ formats. The universe lookup returns the format map (REQ-LIB-8)." Replace "The user sees them in Obsidian's graph and backlinks." with "The user sees a Markdown file's links in Obsidian's graph and backlinks. A DOCX story file's -wikilinks stay clickable in the Console's editor (O2 design D11). The Console -shows a converted chapter's links out and in, in a Connections view." +wikilinks stay clickable in the Console's editor (O2 design D11), and no graph +shows them yet. The Console's Connections view lists the current links and +backlinks of each story file the user may see, in both formats, with each one's +scope and format." Version tag: 'and "Connections are always visible".)' becomes 'and "Connections are always visible". Version 1.17, with Q222 for the two settings.)' @@ -415,8 +417,8 @@ Added after the 1.16 notes: push within about a minute." - REQ-LIB-5, the 1.16 sentence: "The user sees them in Obsidian's graph and backlinks." A converted chapter's connections show in Obsidian only as they - stood at conversion. The Console's Connections view shows their current - links. + stood at conversion, and the Console's Connections view shows their + current links. - REQ-LIB-6, the 1.16 sentence: "A reply may cite lines of the repository at a commit or pages the agent fetched, and the broker checks every citation before it stores the message." @@ -454,7 +456,7 @@ that begins "Trusted mode lets an agent" and before the "## Milestones" heading. - "A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. The DOCX's current links show in the Console's editor and its - Connections view, not in Obsidian. (Version 1.17.)" + Connections view, and no graph shows them yet. (Version 1.17.)" - "Conversion can't be undone in place. Front matter, wiki link forms and unsupported blocks may not survive it, and the mirror can't refuse the user's push to an archived file. The controls are the fidelity report, the human's @@ -471,7 +473,8 @@ that begins "Trusted mode lets an agent" and before the "## Milestones" heading. ## d9 changes (Q239 and Webby round 5) -- J-b yes (Q239, mos-1467): REQ-LIB-5's replacement ends "The Console shows a converted chapter's links out and in, in a Connections view." in place of "and no graph shows them yet". The REQ-LIB-5 note and the graph Risks line name the view as required, not later. J-b and the "Not taken" A6 line record the answer. Nothing else in the PRD text changes. +- J-b yes (Q239, mos-1467), in the five edits mos-1443 R3 set for a yes (Webby round 6 B1). R3.1: REQ-LIB-5's replacement gains the Connections view sentence after "no graph shows them yet.". R3.2: the graph Risks line ends with the editor and the Connections view. R3.3: the A6 line moves from "Not taken" under A6. R3.5: the REQ-LIB-5 note ends with the Connections view, which drops "until a Console view of their links exists" and "Q226 records that view as a later option". R3.4 is Gyro's design edit at 767bb62c7 (writing-editor.md:188-190, :240-244 and :1272, docx-citations.md:66), and it follows in his docs round. Nothing else in the PRD text changes. +- N19 and N20 (Webby round 6): J-b's question text is in the past tense, and the line that the import doesn't wait for the view is cited as Mos's R3 default for him to confirm. - N15: the D7 landing line gives R8's wording beside the impact map's quote. - N16: the d7 changes line notes that R8 replaces "no agent credential reaches it" in d8. - N17: the REQ-LIB-2 Replace quote and the REQ-LIB-8 old-path bullet are rewrapped under 82 columns. Their words are unchanged. @@ -582,6 +585,7 @@ From the impact map, folded as mos-1368 item 1 asked: - A3: the import is outside the vocabulary, the hard-wait list is unchanged, and the archive move isn't `data.delete`. The C6 code site is in the 571 list. - A4: the section lead and REQ-LIB-1's writing-store sentence. - A6: format and location in every answer, extracted text with DOCX locators, links across formats. + - A6's named chapter-links view. D8 took B8's "no graph shows them yet", and J-b put the view to Jason. His O2 (Q239) takes it in d9 as REQ-LIB-5's Connections view (mos-1443 R3). - A7: read-only extends to the store and the archive, no agent action on a story file in any format, no agent DOCX write, and role contracts state the formats. C1's role contract line is a 571 build item. - A8: the DOCX cite shape, and a cite naming an archived file as current is refused. - A9: a hybrid sees a source's DOCX canon through REQ-LIB-2's source scope, and REQ-LIB-8 lets an exclusion name a DOCX document by its id. The id form lets the human exclude a single DOCX started in the editor, which has no old path. An archived file isn't canon, so no hybrid sees it. @@ -602,12 +606,11 @@ Mine, beyond either source: Not taken: - Impact map item 4's "files in unmarked folders are eligible one at a time", for folders outside every book folder and playground only. Their files are unmapped under REQ-LIB-2, so a DOCX made from one would have no universe or book to keep. The human maps such a folder into a book folder or a playground first, under REQ-LIB-1. A file in an unmarked folder inside a book folder or a playground is canon or playground, and the import takes it one file at a time. -- A6's named chapter-links view. D8 takes B8's "no graph shows them yet", and J-b puts the view to Jason. Jason's O2 (Q239) takes the view in d9. ## Marked for Jason (additions in the text he sees) - J-a. Whether "We will not run the systems in parallel" applies per chapter or as one switch per book. His call. As written, it applies per chapter. -- J-b. A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. REQ-LIB-5 still cites two TARGET lines, "Visualization of data via Obsidian or equivalent is required" and "Connections are always visible". Mos's reading is that 1.17 as written meets neither line for converted chapters. Their current links show to the user only as clickable text inside the editor, and no graph or list shows them. Q226 leaves room for "another way to handle the visual brain map". The O2 design that landed for Vikunja 571 at 767bb62c7 holds a Console Connections view and its tests as later work that waits for this answer. His call whether 1.17 requires that view. As written, it does not. Mos recommends that it does, because impact map A6 says "Recommended: name the view" and TARGET says "Connections are always visible". Jason answered O2 (Q239): 1.17 requires the view. d9 writes it into REQ-LIB-5, its note and the Risks line. The view comes with the conversion work after 10-27, the 10-27 Case 2 release stays on Markdown (Q235 P6, Q237), and the import does not wait for the view (mos-1443 R3). +- J-b. A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. REQ-LIB-5 still cites two TARGET lines, "Visualization of data via Obsidian or equivalent is required" and "Connections are always visible". Mos's reading was that 1.17 as d8 wrote it met neither line for converted chapters. Their current links showed to the user only as clickable text inside the editor, and no graph or list showed them. Q226 leaves room for "another way to handle the visual brain map". The O2 design that landed for Vikunja 571 at 767bb62c7 held a Console Connections view and its tests as later work that waited for this answer. His call was whether 1.17 requires that view. As d8 was written, it did not. Mos recommended that it does, because impact map A6 says "Recommended: name the view" and TARGET says "Connections are always visible". Jason answered O2 (Q239): 1.17 requires the view. d9 writes it into REQ-LIB-5, its note and the Risks line, in the text of mos-1443 R3. The view comes with the conversion work after 10-27, and the 10-27 Case 2 release stays on Markdown (Q235 P6, Q237). That the import does not wait for the view is Mos's default in mos-1443 R3. Q239 doesn't address it, and Mos confirms or changes it at his J-b check. - J-c (mos-1374): "The store pushes to a remote (D7), and the Case 2 VM is in the nightly PBS backup. For a fixed restore point before her first real import, a manual backup of VM 1012 with PBS protect runs first. That step is reversible and needs no reboot." Mos's reading is that this sits inside the P5 go step, so it needs no new question. - J-d. How agents read a converted chapter, D9. His call. As written, an agent reads it through the ordinary Case 2 lookups in any thread or room, under the same project and universe access as Markdown canon. This is Mos's reading of F41 and REQ-LIB-7. The other choice is the model in the earlier O2 design, W4 sections 7.1 and 7.2. Under it, an agent reads a converted chapter only in a new writing conversation that holds one human and one agent, only after the business owner grants that agent access to that document, and by default only what the human attaches to each message. Comments and tracked deletions stay hidden from agents until a human turns on a setting for each. Markdown has neither, so the default keeps agents at the access Markdown gives them. Those two sentences are Mos's ruling mos-1379. A yes to the text as written settles it. - J-e. Versioning means the editor's tracked changes plus one git commit per save. diff --git a/agents/sage/work/prd-1-17/DRAFT.md b/agents/sage/work/prd-1-17/DRAFT.md index b1ca59160..7d5c03273 100644 --- a/agents/sage/work/prd-1-17/DRAFT.md +++ b/agents/sage/work/prd-1-17/DRAFT.md @@ -1,6 +1,6 @@ # PRD 1.17 draft: Case 2 story files are DOCX (Q235 to Q237, P1 to P6) -Sage, 2026-10-23, for mos-1366 item 1 and Vikunja 570. Draft 9. It is d8 plus Jason's Q41 answer O2 (DECISIONS Q239, mos-1467), which makes J-b yes, and Webby's round 5 N15 to N17 (webby-0210) (see "d9 changes"). d8 is d7 plus Mos's d8 fix list mos-1443 (see "d8 changes"). d7 is d6 plus Mos's ruling mos-1379 on Fenton's 571 B2 (see "d7 changes"). d6 is d5 with Webby's round 3 (webby-0207) fixed: B1 to B3 and N10 to N13, with N14 left for Mos (see "d6 changes"). d5 folds in: +Sage, 2026-10-23, for mos-1366 item 1 and Vikunja 570. Draft 9. It is d8 plus Jason's Q41 answer O2 (DECISIONS Q239, mos-1467), which makes J-b yes, Webby's round 5 N15 to N17 (webby-0210) and Webby's round 6 B1, N19 and N20 (webby-0212) (see "d9 changes"). d8 is d7 plus Mos's d8 fix list mos-1443 (see "d8 changes"). d7 is d6 plus Mos's ruling mos-1379 on Fenton's 571 B2 (see "d7 changes"). d6 is d5 with Webby's round 3 (webby-0207) fixed: B1 to B3 and N10 to N13, with N14 left for Mos (see "d6 changes"). d5 folds in: - Mos's d4 check ruling mos-1372 (D1 to D14; D15 was dropped). - mos-1374, which replaces J-c. - The impact map mos-1368 (jason-master-restart d183246, `projects/mosaic-mvp/case2-docx-impact-map.md`: A1 to A16, critic items C1 to C6, items 2 to 7). @@ -191,8 +191,10 @@ formats. The universe lookup returns the format map (REQ-LIB-8)." Replace "The user sees them in Obsidian's graph and backlinks." with "The user sees a Markdown file's links in Obsidian's graph and backlinks. A DOCX story file's -wikilinks stay clickable in the Console's editor (O2 design D11). The Console -shows a converted chapter's links out and in, in a Connections view." +wikilinks stay clickable in the Console's editor (O2 design D11), and no graph +shows them yet. The Console's Connections view lists the current links and +backlinks of each story file the user may see, in both formats, with each one's +scope and format." Version tag: 'and "Connections are always visible".)' becomes 'and "Connections are always visible". Version 1.17, with Q222 for the two settings.)' @@ -415,8 +417,8 @@ Added after the 1.16 notes: push within about a minute." - REQ-LIB-5, the 1.16 sentence: "The user sees them in Obsidian's graph and backlinks." A converted chapter's connections show in Obsidian only as they - stood at conversion. The Console's Connections view shows their current - links. + stood at conversion, and the Console's Connections view shows their + current links. - REQ-LIB-6, the 1.16 sentence: "A reply may cite lines of the repository at a commit or pages the agent fetched, and the broker checks every citation before it stores the message." @@ -454,7 +456,7 @@ that begins "Trusted mode lets an agent" and before the "## Milestones" heading. - "A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. The DOCX's current links show in the Console's editor and its - Connections view, not in Obsidian. (Version 1.17.)" + Connections view, and no graph shows them yet. (Version 1.17.)" - "Conversion can't be undone in place. Front matter, wiki link forms and unsupported blocks may not survive it, and the mirror can't refuse the user's push to an archived file. The controls are the fidelity report, the human's @@ -471,7 +473,8 @@ that begins "Trusted mode lets an agent" and before the "## Milestones" heading. ## d9 changes (Q239 and Webby round 5) -- J-b yes (Q239, mos-1467): REQ-LIB-5's replacement ends "The Console shows a converted chapter's links out and in, in a Connections view." in place of "and no graph shows them yet". The REQ-LIB-5 note and the graph Risks line name the view as required, not later. J-b and the "Not taken" A6 line record the answer. Nothing else in the PRD text changes. +- J-b yes (Q239, mos-1467), in the five edits mos-1443 R3 set for a yes (Webby round 6 B1). R3.1: REQ-LIB-5's replacement gains the Connections view sentence after "no graph shows them yet.". R3.2: the graph Risks line ends with the editor and the Connections view. R3.3: the A6 line moves from "Not taken" under A6. R3.5: the REQ-LIB-5 note ends with the Connections view, which drops "until a Console view of their links exists" and "Q226 records that view as a later option". R3.4 is Gyro's design edit at 767bb62c7 (writing-editor.md:188-190, :240-244 and :1272, docx-citations.md:66), and it follows in his docs round. Nothing else in the PRD text changes. +- N19 and N20 (Webby round 6): J-b's question text is in the past tense, and the line that the import doesn't wait for the view is cited as Mos's R3 default for him to confirm. - N15: the D7 landing line gives R8's wording beside the impact map's quote. - N16: the d7 changes line notes that R8 replaces "no agent credential reaches it" in d8. - N17: the REQ-LIB-2 Replace quote and the REQ-LIB-8 old-path bullet are rewrapped under 82 columns. Their words are unchanged. @@ -582,6 +585,7 @@ From the impact map, folded as mos-1368 item 1 asked: - A3: the import is outside the vocabulary, the hard-wait list is unchanged, and the archive move isn't `data.delete`. The C6 code site is in the 571 list. - A4: the section lead and REQ-LIB-1's writing-store sentence. - A6: format and location in every answer, extracted text with DOCX locators, links across formats. + - A6's named chapter-links view. D8 took B8's "no graph shows them yet", and J-b put the view to Jason. His O2 (Q239) takes it in d9 as REQ-LIB-5's Connections view (mos-1443 R3). - A7: read-only extends to the store and the archive, no agent action on a story file in any format, no agent DOCX write, and role contracts state the formats. C1's role contract line is a 571 build item. - A8: the DOCX cite shape, and a cite naming an archived file as current is refused. - A9: a hybrid sees a source's DOCX canon through REQ-LIB-2's source scope, and REQ-LIB-8 lets an exclusion name a DOCX document by its id. The id form lets the human exclude a single DOCX started in the editor, which has no old path. An archived file isn't canon, so no hybrid sees it. @@ -602,12 +606,11 @@ Mine, beyond either source: Not taken: - Impact map item 4's "files in unmarked folders are eligible one at a time", for folders outside every book folder and playground only. Their files are unmapped under REQ-LIB-2, so a DOCX made from one would have no universe or book to keep. The human maps such a folder into a book folder or a playground first, under REQ-LIB-1. A file in an unmarked folder inside a book folder or a playground is canon or playground, and the import takes it one file at a time. -- A6's named chapter-links view. D8 takes B8's "no graph shows them yet", and J-b puts the view to Jason. Jason's O2 (Q239) takes the view in d9. ## Marked for Jason (additions in the text he sees) - J-a. Whether "We will not run the systems in parallel" applies per chapter or as one switch per book. His call. As written, it applies per chapter. -- J-b. A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. REQ-LIB-5 still cites two TARGET lines, "Visualization of data via Obsidian or equivalent is required" and "Connections are always visible". Mos's reading is that 1.17 as written meets neither line for converted chapters. Their current links show to the user only as clickable text inside the editor, and no graph or list shows them. Q226 leaves room for "another way to handle the visual brain map". The O2 design that landed for Vikunja 571 at 767bb62c7 holds a Console Connections view and its tests as later work that waits for this answer. His call whether 1.17 requires that view. As written, it does not. Mos recommends that it does, because impact map A6 says "Recommended: name the view" and TARGET says "Connections are always visible". Jason answered O2 (Q239): 1.17 requires the view. d9 writes it into REQ-LIB-5, its note and the Risks line. The view comes with the conversion work after 10-27, the 10-27 Case 2 release stays on Markdown (Q235 P6, Q237), and the import does not wait for the view (mos-1443 R3). +- J-b. A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. REQ-LIB-5 still cites two TARGET lines, "Visualization of data via Obsidian or equivalent is required" and "Connections are always visible". Mos's reading was that 1.17 as d8 wrote it met neither line for converted chapters. Their current links showed to the user only as clickable text inside the editor, and no graph or list showed them. Q226 leaves room for "another way to handle the visual brain map". The O2 design that landed for Vikunja 571 at 767bb62c7 held a Console Connections view and its tests as later work that waited for this answer. His call was whether 1.17 requires that view. As d8 was written, it did not. Mos recommended that it does, because impact map A6 says "Recommended: name the view" and TARGET says "Connections are always visible". Jason answered O2 (Q239): 1.17 requires the view. d9 writes it into REQ-LIB-5, its note and the Risks line, in the text of mos-1443 R3. The view comes with the conversion work after 10-27, and the 10-27 Case 2 release stays on Markdown (Q235 P6, Q237). That the import does not wait for the view is Mos's default in mos-1443 R3. Q239 doesn't address it, and Mos confirms or changes it at his J-b check. - J-c (mos-1374): "The store pushes to a remote (D7), and the Case 2 VM is in the nightly PBS backup. For a fixed restore point before her first real import, a manual backup of VM 1012 with PBS protect runs first. That step is reversible and needs no reboot." Mos's reading is that this sits inside the P5 go step, so it needs no new question. - J-d. How agents read a converted chapter, D9. His call. As written, an agent reads it through the ordinary Case 2 lookups in any thread or room, under the same project and universe access as Markdown canon. This is Mos's reading of F41 and REQ-LIB-7. The other choice is the model in the earlier O2 design, W4 sections 7.1 and 7.2. Under it, an agent reads a converted chapter only in a new writing conversation that holds one human and one agent, only after the business owner grants that agent access to that document, and by default only what the human attaches to each message. Comments and tracked deletions stay hidden from agents until a human turns on a setting for each. Markdown has neither, so the default keeps agents at the access Markdown gives them. Those two sentences are Mos's ruling mos-1379. A yes to the text as written settles it. - J-e. Versioning means the editor's tracked changes plus one git commit per save. diff --git a/agents/sage/work/prd-1-17/d8-to-d9.diff b/agents/sage/work/prd-1-17/d8-to-d9.diff index 0a5971c56..323f6afbe 100644 --- a/agents/sage/work/prd-1-17/d8-to-d9.diff +++ b/agents/sage/work/prd-1-17/d8-to-d9.diff @@ -1,10 +1,10 @@ --- DRAFT-d8.md 2026-10-23 06:16:54.374694135 -0500 -+++ DRAFT-d9.md 2026-10-23 10:25:28.160826165 -0500 ++++ DRAFT-d9.md 2026-10-23 10:36:11.109422593 -0500 @@ -1,6 +1,6 @@ # PRD 1.17 draft: Case 2 story files are DOCX (Q235 to Q237, P1 to P6) -Sage, 2026-10-23, for mos-1366 item 1 and Vikunja 570. Draft 8. It is d7 plus Mos's d8 fix list mos-1443 (see "d8 changes"). d7 is d6 plus Mos's ruling mos-1379 on Fenton's 571 B2 (see "d7 changes"). d6 is d5 with Webby's round 3 (webby-0207) fixed: B1 to B3 and N10 to N13, with N14 left for Mos (see "d6 changes"). d5 folds in: -+Sage, 2026-10-23, for mos-1366 item 1 and Vikunja 570. Draft 9. It is d8 plus Jason's Q41 answer O2 (DECISIONS Q239, mos-1467), which makes J-b yes, and Webby's round 5 N15 to N17 (webby-0210) (see "d9 changes"). d8 is d7 plus Mos's d8 fix list mos-1443 (see "d8 changes"). d7 is d6 plus Mos's ruling mos-1379 on Fenton's 571 B2 (see "d7 changes"). d6 is d5 with Webby's round 3 (webby-0207) fixed: B1 to B3 and N10 to N13, with N14 left for Mos (see "d6 changes"). d5 folds in: ++Sage, 2026-10-23, for mos-1366 item 1 and Vikunja 570. Draft 9. It is d8 plus Jason's Q41 answer O2 (DECISIONS Q239, mos-1467), which makes J-b yes, Webby's round 5 N15 to N17 (webby-0210) and Webby's round 6 B1, N19 and N20 (webby-0212) (see "d9 changes"). d8 is d7 plus Mos's d8 fix list mos-1443 (see "d8 changes"). d7 is d6 plus Mos's ruling mos-1379 on Fenton's 571 B2 (see "d7 changes"). d6 is d5 with Webby's round 3 (webby-0207) fixed: B1 to B3 and N10 to N13, with N14 left for Mos (see "d6 changes"). d5 folds in: - Mos's d4 check ruling mos-1372 (D1 to D14; D15 was dropped). - mos-1374, which replaces J-c. - The impact map mos-1368 (jason-master-restart d183246, `projects/mosaic-mvp/case2-docx-impact-map.md`: A1 to A16, critic items C1 to C6, items 2 to 7). @@ -24,18 +24,18 @@ "A Markdown file's scope comes from its path and from past imports, prefixes first: a Markdown file under the archive folder is archived, one under a -@@ -190,8 +191,8 @@ - +@@ -191,7 +192,9 @@ Replace "The user sees them in Obsidian's graph and backlinks." with "The user sees a Markdown file's links in Obsidian's graph and backlinks. A DOCX story file's --wikilinks stay clickable in the Console's editor (O2 design D11), and no graph + wikilinks stay clickable in the Console's editor (O2 design D11), and no graph -shows them yet." -+wikilinks stay clickable in the Console's editor (O2 design D11). The Console -+shows a converted chapter's links out and in, in a Connections view." ++shows them yet. The Console's Connections view lists the current links and ++backlinks of each story file the user may see, in both formats, with each one's ++scope and format." Version tag: 'and "Connections are always visible".)' becomes 'and "Connections are always visible". Version 1.17, with Q222 for the two settings.)' -@@ -273,8 +274,9 @@ +@@ -273,8 +276,9 @@ - Each stage of an import writes a logged event. The import's record on the stack's host names the source file's path, commit and blob and the new document id, and each event points to that record. @@ -47,35 +47,36 @@ - A new Markdown story file in a book folder that holds converted files stays canon until its import, unless it sits at a converted file's old path or under a playground prefix. The Console flags it and offers the import. Nothing -@@ -413,8 +415,8 @@ +@@ -413,8 +417,8 @@ push within about a minute." - REQ-LIB-5, the 1.16 sentence: "The user sees them in Obsidian's graph and backlinks." A converted chapter's connections show in Obsidian only as they - stood at conversion, until a Console view of their links exists. Q226 - records that view as a later option. -+ stood at conversion. The Console's Connections view shows their current -+ links. ++ stood at conversion, and the Console's Connections view shows their ++ current links. - REQ-LIB-6, the 1.16 sentence: "A reply may cite lines of the repository at a commit or pages the agent fetched, and the broker checks every citation before it stores the message." -@@ -451,8 +453,8 @@ +@@ -451,8 +455,8 @@ not `git diff`. (Version 1.17.)" - "A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's - links. The DOCX's current links show only in the Console's editor until a - Console view of them exists. (Version 1.17.)" + links. The DOCX's current links show in the Console's editor and its -+ Connections view, not in Obsidian. (Version 1.17.)" ++ Connections view, and no graph shows them yet. (Version 1.17.)" - "Conversion can't be undone in place. Front matter, wiki link forms and unsupported blocks may not survive it, and the mirror can't refuse the user's push to an archived file. The controls are the fidelity report, the human's -@@ -467,6 +469,13 @@ +@@ -467,6 +471,14 @@ import events, and the import's recovery covers both cases (Vikunja 571). (Version 1.17.)" +## d9 changes (Q239 and Webby round 5) + -+- J-b yes (Q239, mos-1467): REQ-LIB-5's replacement ends "The Console shows a converted chapter's links out and in, in a Connections view." in place of "and no graph shows them yet". The REQ-LIB-5 note and the graph Risks line name the view as required, not later. J-b and the "Not taken" A6 line record the answer. Nothing else in the PRD text changes. ++- J-b yes (Q239, mos-1467), in the five edits mos-1443 R3 set for a yes (Webby round 6 B1). R3.1: REQ-LIB-5's replacement gains the Connections view sentence after "no graph shows them yet.". R3.2: the graph Risks line ends with the editor and the Connections view. R3.3: the A6 line moves from "Not taken" under A6. R3.5: the REQ-LIB-5 note ends with the Connections view, which drops "until a Console view of their links exists" and "Q226 records that view as a later option". R3.4 is Gyro's design edit at 767bb62c7 (writing-editor.md:188-190, :240-244 and :1272, docx-citations.md:66), and it follows in his docs round. Nothing else in the PRD text changes. ++- N19 and N20 (Webby round 6): J-b's question text is in the past tense, and the line that the import doesn't wait for the view is cited as Mos's R3 default for him to confirm. +- N15: the D7 landing line gives R8's wording beside the impact map's quote. +- N16: the d7 changes line notes that R8 replaces "no agent credential reaches it" in d8. +- N17: the REQ-LIB-2 Replace quote and the REQ-LIB-8 old-path bullet are rewrapped under 82 columns. Their words are unchanged. @@ -83,7 +84,7 @@ ## d8 changes (Mos's d8 fix list, check wf_63bba879-180) - R1: REQ-LIB-4's tail covers DOCX saves, which agents see at their next lookup after the editor reports them as committed. The notes quote the whole 1.16 sentence. Source: nit/jason/F10. -@@ -535,7 +544,7 @@ +@@ -535,7 +547,7 @@ - REQ-LIB-5 gains Mos's three sentences after the extracted-text sentence. The text agents read has tracked changes accepted. Comments, and text with tracked deletions shown, each wait for a setting only a human turns on, off by default. Its version tag cites Q222 for the two settings, which is the only text here beyond Mos's. - J-d gains Mos's sentence on comments and tracked deletions. @@ -92,7 +93,7 @@ ## d6 changes (Webby round 3, webby-0207) -@@ -556,7 +565,7 @@ +@@ -556,7 +568,7 @@ - D4: REQ-LIB-8's one-way bullet, which carries the archive refusal and consequence F2's text, and the 571 list item. - D5: it landed in REQ-LIB-2's "a Markdown file at a converted file's old path is unmapped" in Webby's B2 form, and in the REQ-LIB-8 old-path bullet. - D6: REQ-LIB-5's freshness sentences. @@ -101,18 +102,25 @@ - D8: the REQ-LIB-5 replacement, the import bullet's wiki-link sentence, the Risks line, the note quoting the old sentence, and "REQ-LIB-1 only gains sentences". - D9: the 1.17 note that agents read a converted story file through the Case 2 lookups, from the d4 check's consistency B2, and J-d, which puts the read model to Jason as his call. - D10: the d4 check's B5 sentence, in REQ-LIB-8. -@@ -593,12 +602,12 @@ +@@ -573,6 +585,7 @@ + - A3: the import is outside the vocabulary, the hard-wait list is unchanged, and the archive move isn't `data.delete`. The C6 code site is in the 571 list. + - A4: the section lead and REQ-LIB-1's writing-store sentence. + - A6: format and location in every answer, extracted text with DOCX locators, links across formats. ++ - A6's named chapter-links view. D8 took B8's "no graph shows them yet", and J-b put the view to Jason. His O2 (Q239) takes it in d9 as REQ-LIB-5's Connections view (mos-1443 R3). + - A7: read-only extends to the store and the archive, no agent action on a story file in any format, no agent DOCX write, and role contracts state the formats. C1's role contract line is a 571 build item. + - A8: the DOCX cite shape, and a cite naming an archived file as current is refused. + - A9: a hybrid sees a source's DOCX canon through REQ-LIB-2's source scope, and REQ-LIB-8 lets an exclusion name a DOCX document by its id. The id form lets the human exclude a single DOCX started in the editor, which has no old path. An archived file isn't canon, so no hybrid sees it. +@@ -593,12 +606,11 @@ Not taken: - Impact map item 4's "files in unmarked folders are eligible one at a time", for folders outside every book folder and playground only. Their files are unmapped under REQ-LIB-2, so a DOCX made from one would have no universe or book to keep. The human maps such a folder into a book folder or a playground first, under REQ-LIB-1. A file in an unmarked folder inside a book folder or a playground is canon or playground, and the import takes it one file at a time. -- A6's named chapter-links view. D8 takes B8's "no graph shows them yet", and J-b puts the view to Jason. -+- A6's named chapter-links view. D8 takes B8's "no graph shows them yet", and J-b puts the view to Jason. Jason's O2 (Q239) takes the view in d9. ## Marked for Jason (additions in the text he sees) - J-a. Whether "We will not run the systems in parallel" applies per chapter or as one switch per book. His call. As written, it applies per chapter. -- J-b. A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. REQ-LIB-5 still cites two TARGET lines, "Visualization of data via Obsidian or equivalent is required" and "Connections are always visible". Mos's reading is that 1.17 as written meets neither line for converted chapters. Their current links show to the user only as clickable text inside the editor, and no graph or list shows them. Q226 leaves room for "another way to handle the visual brain map". The O2 design that landed for Vikunja 571 at 767bb62c7 holds a Console Connections view and its tests as later work that waits for this answer. His call whether 1.17 requires that view. As written, it does not. Mos recommends that it does, because impact map A6 says "Recommended: name the view" and TARGET says "Connections are always visible". -+- J-b. A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. REQ-LIB-5 still cites two TARGET lines, "Visualization of data via Obsidian or equivalent is required" and "Connections are always visible". Mos's reading is that 1.17 as written meets neither line for converted chapters. Their current links show to the user only as clickable text inside the editor, and no graph or list shows them. Q226 leaves room for "another way to handle the visual brain map". The O2 design that landed for Vikunja 571 at 767bb62c7 holds a Console Connections view and its tests as later work that waits for this answer. His call whether 1.17 requires that view. As written, it does not. Mos recommends that it does, because impact map A6 says "Recommended: name the view" and TARGET says "Connections are always visible". Jason answered O2 (Q239): 1.17 requires the view. d9 writes it into REQ-LIB-5, its note and the Risks line. The view comes with the conversion work after 10-27, the 10-27 Case 2 release stays on Markdown (Q235 P6, Q237), and the import does not wait for the view (mos-1443 R3). ++- J-b. A converted chapter's DOCX is not in Obsidian's graph. Obsidian shows the chapter only through its archived Markdown, and no DOCX edit reaches that file's links. REQ-LIB-5 still cites two TARGET lines, "Visualization of data via Obsidian or equivalent is required" and "Connections are always visible". Mos's reading was that 1.17 as d8 wrote it met neither line for converted chapters. Their current links showed to the user only as clickable text inside the editor, and no graph or list showed them. Q226 leaves room for "another way to handle the visual brain map". The O2 design that landed for Vikunja 571 at 767bb62c7 held a Console Connections view and its tests as later work that waited for this answer. His call was whether 1.17 requires that view. As d8 was written, it did not. Mos recommended that it does, because impact map A6 says "Recommended: name the view" and TARGET says "Connections are always visible". Jason answered O2 (Q239): 1.17 requires the view. d9 writes it into REQ-LIB-5, its note and the Risks line, in the text of mos-1443 R3. The view comes with the conversion work after 10-27, and the 10-27 Case 2 release stays on Markdown (Q235 P6, Q237). That the import does not wait for the view is Mos's default in mos-1443 R3. Q239 doesn't address it, and Mos confirms or changes it at his J-b check. - J-c (mos-1374): "The store pushes to a remote (D7), and the Case 2 VM is in the nightly PBS backup. For a fixed restore point before her first real import, a manual backup of VM 1012 with PBS protect runs first. That step is reversible and needs no reboot." Mos's reading is that this sits inside the P5 go step, so it needs no new question. - J-d. How agents read a converted chapter, D9. His call. As written, an agent reads it through the ordinary Case 2 lookups in any thread or room, under the same project and universe access as Markdown canon. This is Mos's reading of F41 and REQ-LIB-7. The other choice is the model in the earlier O2 design, W4 sections 7.1 and 7.2. Under it, an agent reads a converted chapter only in a new writing conversation that holds one human and one agent, only after the business owner grants that agent access to that document, and by default only what the human attaches to each message. Comments and tracked deletions stay hidden from agents until a human turns on a setting for each. Markdown has neither, so the default keeps agents at the access Markdown gives them. Those two sentences are Mos's ruling mos-1379. A yes to the text as written settles it. - J-e. Versioning means the editor's tracked changes plus one git commit per save.