From 90043ab6bf44c9f19dc044ffc0c3d6896717e6c1 Mon Sep 17 00:00:00 2001 From: "david.delagneau" Date: Thu, 16 Apr 2026 15:31:19 -0600 Subject: [PATCH] feat: Update documentation and configuration for onboarding, graph defaults, and workspace navigation --- .obsidian/graph.json | 6 +++--- ai/logs/2026-04-16.md | 4 ++++ ai/state/current.md | 2 ++ ai/work-items/pdiap-15765.md | 4 ++++ knowledge/maps/ai-workspace-core.md | 2 ++ knowledge/maps/people.md | 2 ++ knowledge/maps/tooling.md | 1 + knowledge/maps/work-items.md | 1 + knowledge/obsidian-usage.md | 29 +++++++++++++++++++++++++++++ 9 files changed, 48 insertions(+), 3 deletions(-) diff --git a/.obsidian/graph.json b/.obsidian/graph.json index 17f5818..6b13a4c 100644 --- a/.obsidian/graph.json +++ b/.obsidian/graph.json @@ -1,10 +1,10 @@ { "collapse-filter": true, - "search": "-path:.git -path:.opencode/node_modules -path:ai/inbox -path:archives -path:scripts/mattermost/generated -path:scripts/slack/generated -path:scripts/mattermost/.venv -path:scripts/slack/.venv -path:generated -path:.venv", + "search": "-path:.git -path:.opencode/node_modules -path:ai/inbox -path:archives -path:scripts/mattermost/generated -path:scripts/slack/generated -path:scripts/mattermost/.venv -path:scripts/slack/.venv -path:generated -path:.venv -file:index -file:README -file:AGENTS -file:SKILL", "showTags": true, "showAttachments": false, "hideUnresolved": false, - "showOrphans": true, + "showOrphans": false, "collapse-color-groups": true, "colorGroups": [ { @@ -46,6 +46,6 @@ "repelStrength": 10, "linkStrength": 1, "linkDistance": 250, - "scale": 1.0862826017262757, + "scale": 2.0503081104007936, "close": true } \ No newline at end of file diff --git a/ai/logs/2026-04-16.md b/ai/logs/2026-04-16.md index 8a5e8b0..a8c6111 100644 --- a/ai/logs/2026-04-16.md +++ b/ai/logs/2026-04-16.md @@ -25,3 +25,7 @@ - Jeff concluded there is no point relying on a separate service release for the Youth issue if it would also require its own rollout; the iOS PR should be treated as the primary fix path, while the QA-side flow-definition change explains why the issue no longer reproduces in XQ1. - Durable tooling/system note: in Fidelity flow work, Cogstore is the platform used to modify and publish many individual flow configurations, compare versions per flow, and check who/when a specific flow version was published to QA or Production. Slate was the newer consumer-side configuration tooling during the SwiftUI refactor, but Jeff believes it is now decommissioned. - Additional tooling note: flow IDs are not guaranteed to exist in both Cogstore and Slate, so the active configuration source for a given flow should be verified instead of assumed. +- David confirmed that the `HybridBrokerageAccountOpening` / `JointIdentityCheck` flow-definition content is the same in QA and Production even though the versions differ (`0.0.267` vs `0.0.263`), so that separate rule-content issue should also be reproducible in Production. +- Jeff asked Rashmi to revert the Youth-flow service change so the iOS-side PR can remain the single fix path for that issue. +- David confirmed Rashmi reverted the QA change by publishing the earlier flow version, and local Fid4 validation with the iOS PR showed the `birthDate`-based validation now works as expected. +- Jeff's preferred external summary is now very explicit: we went back and fixed their original iOS-only issue on the iOS side, while the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue is a new service-side problem that still needs its own follow-up. diff --git a/ai/state/current.md b/ai/state/current.md index e8a9dba..864b95f 100644 --- a/ai/state/current.md +++ b/ai/state/current.md @@ -22,11 +22,13 @@ - The rollout document should use the new flag name `xflow-swiftui-container-enabled` and note that the flag will be added later during implementation - Re-check the authenticated AO validation issue with scenario-specific evidence: the `HybridYouthAccountOpening` / `TeenIdentityCheck` path currently points to an iOS-only decoding gap, while a separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` case reproduces on both platforms - The immediate Youth issue was fixed on the service side for the Youth-flow `TeenIdentityCheck` path after the payload moved from `birthDate` to `validations`; local Fid4 validation also confirmed it. The XFlowSDK-side fallback PR should still ship in the next release +- Jeff later decided the iOS fallback PR should be treated as the primary fix path for the Youth issue rather than relying on a separate service rollout; the QA-side service change has since been rolled back and Fid4 validation still passed with the PR in place - When describing the XFlowSDK fallback PR, frame it as a compatibility improvement for similar future `birthDate` payloads, not as a fix for the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue - The Youth / `TeenIdentityCheck` issue was iOS-only; do not describe it as reproducing on both platforms - The service-side payload update and the XFlowSDK fallback PR address the same Youth / `TeenIdentityCheck` issue; do not split them into separate Youth issues when summarizing scope - `PDIAP-15765` should stay out of Done until the PR is merged; Santosh approved it, but code-owner approval is still required before merge - Before closing out the AO thread, send one more working-group Teams reply that summarizes the original iOS issue, links the Jira comment, Discourse comment, and PR, and separates the remaining `HybridBrokerageAccountOpening` / `JointIdentityCheck` service-side issue +- The `HybridBrokerageAccountOpening` / `JointIdentityCheck` rule-content issue appears unchanged between QA and Production in Cogstore and should be treated as the remaining service-side follow-up --- diff --git a/ai/work-items/pdiap-15765.md b/ai/work-items/pdiap-15765.md index e753eef..ea6302b 100644 --- a/ai/work-items/pdiap-15765.md +++ b/ai/work-items/pdiap-15765.md @@ -30,6 +30,7 @@ - Later validation on April 15 showed the original `HybridYouthAccountOpening` / `TeenIdentityCheck` issue no longer reproduces once the payload uses `validations` instead of `birthDate`. - A minimal XFlowSDK fix was still prepared on April 15 so the iOS `.apxDateSelect` path also falls back to `birthDate` for a future release. - Jeff confirmed on April 15 that this minimal iOS fallback is the right fix direction for the Youth / `TeenIdentityCheck` case and approved opening the PR under the same story. +- On April 16, Jeff decided the iOS PR should be the primary fix path for the Youth / `TeenIdentityCheck` issue rather than relying on a separate service rollout. --- @@ -40,8 +41,10 @@ - Keep the authenticated-user qualifier whenever this ticket is mentioned. - Do not describe it as a generic validation issue without the `TeenIdentityCheck` and auth context. - The originally reported Youth issue was fixed for the Youth-flow `TeenIdentityCheck` path by the service-side payload update from `birthDate` to `validations`; local Fid4 validation also confirmed it. The XFlowSDK fallback PR should still be released so iOS handles the older `birthDate` format more safely. +- That service-side Youth fix was later rolled back in QA so the iOS PR can remain the single fix path; local Fid4 validation with the PR still confirmed the `birthDate` validation works correctly. - Jeff provided historical context that these fallback paths exist largely to accommodate older AO payload conventions; when the issue is AO-specific, iOS-only, and caused by a service-vs-SDK key mismatch, this kind of iOS fallback is the usual fix. - The `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue is different from the original Youth report: the rule content itself does not include `ageRange` or `eighteenOrAbove`, so that path still points to a service-side update rather than the same iOS parsing gap. +- David compared `HybridBrokerageAccountOpening` / `JointIdentityCheck` in Cogstore and found the relevant rule content is the same in QA and Production despite different flow-definition versions, so that separate issue should also exist in Production. - The small iOS PR should be described as a compatibility safeguard for future older-format payloads and should not be framed as applying to the `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue. - The service-side `birthDate` -> `validations` change and the small iOS PR both relate to the same Youth / `TeenIdentityCheck` issue; they should not be described as separate Youth issues. @@ -52,6 +55,7 @@ - Get the small XFlowSDK compatibility PR reviewed and released. - Send one more AO working-group Teams summary that points to the Jira comment, Discourse comment, and PR while keeping the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue clearly out of the original Youth-fix scope. - Keep the final AO working-group message very explicit about there being two flow scenarios: the Youth iOS-only issue now handled by the service change plus iOS fallback, and the separate cross-platform `HybridBrokerageAccountOpening` / `JointIdentityCheck` service-side issue. +- Update that AO working-group message so it now reflects the final framing: the original Youth issue is fixed on the iOS side, and the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue is the remaining service-side follow-up. - Close the story with comments explaining that the immediate Youth issue was resolved on the service side and that the XFlowSDK fallback fix will be available in the next release. - Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of the client-fix scope unless later evidence proves it is part of the same issue. - Consider a separate follow-up ticket for the cross-platform service-side issue if that path still stands after consumer confirmation. diff --git a/knowledge/maps/ai-workspace-core.md b/knowledge/maps/ai-workspace-core.md index c572f78..ebb209d 100644 --- a/knowledge/maps/ai-workspace-core.md +++ b/knowledge/maps/ai-workspace-core.md @@ -14,6 +14,8 @@ Reusable workspace logic and project-independent operating rules. ## Core Model +- [New Member Onboarding](../onboarding.md) +- [Obsidian Usage Guide](../obsidian-usage.md) - [Core Overview](../../core/README.md) - [Operational Memory](../../core/memory/operational-memory.md) - [Communication Integration Model](../../core/integrations/communication-model.md) diff --git a/knowledge/maps/people.md b/knowledge/maps/people.md index f3da61d..64fadf0 100644 --- a/knowledge/maps/people.md +++ b/knowledge/maps/people.md @@ -14,6 +14,8 @@ Stakeholder, manager, and collaborator context. ## Indexes +- [New Member Onboarding](../onboarding.md) +- [Glossary](../glossary.md) - [People Index](../../ai/context/people/index.md) - [Manager Mapping](../../ai/context/people/manager.md) diff --git a/knowledge/maps/tooling.md b/knowledge/maps/tooling.md index db96130..eaad0e2 100644 --- a/knowledge/maps/tooling.md +++ b/knowledge/maps/tooling.md @@ -14,6 +14,7 @@ Commands, prompts, skills, workflows, and automation surfaces that make the work ## OpenCode Agents +- [AI Workspace Core Map](ai-workspace-core.md) - [Fidelity Agent](../../.opencode/agents/fidelity.md) - [Workspace Agent](../../.opencode/agents/workspace.md) diff --git a/knowledge/maps/work-items.md b/knowledge/maps/work-items.md index 72a9d9a..20d5ca3 100644 --- a/knowledge/maps/work-items.md +++ b/knowledge/maps/work-items.md @@ -14,6 +14,7 @@ Canonical memory for active and recently relevant work units. ## Indexes +- [Current Work Map](current-work.md) - [Work Item Index](../../ai/work-items/index.md) - [Work Item State](../../ai/state/work-items.md) - [Current Work](../../ai/state/current.md) diff --git a/knowledge/obsidian-usage.md b/knowledge/obsidian-usage.md index baef869..64daa30 100644 --- a/knowledge/obsidian-usage.md +++ b/knowledge/obsidian-usage.md @@ -75,6 +75,35 @@ If a node is isolated, it may still be valid. It may be: --- +## Global Graph Defaults + +The global graph is configured for onboarding and project navigation, not full filesystem inspection. + +It intentionally hides generic technical filenames such as: + +- `index` +- `README` +- `AGENTS` +- `SKILL` + +Those files still exist and remain valid workspace files. They are hidden from the graph because Obsidian displays only the basename, which creates many indistinguishable nodes. + +Use the file explorer or search when you need a specific technical file. Use the graph when you want to understand relationships between project concepts. + +--- + +## When To Show Technical Files + +Temporarily remove these filters from the graph search when debugging workspace internals: + +```text +-file:index -file:README -file:AGENTS -file:SKILL +``` + +For normal onboarding, keep them hidden and navigate through the named maps. + +--- + ## Editing Rules - Edit canonical memory files when the fact is clear.