rhachet-roles-bhrain 0.1.0 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/roles/architect/briefs/brains.replic/arc000.sources.[catalog].md +178 -0
- package/dist/roles/architect/briefs/brains.replic/arc101.concept.llm.[article].md +25 -0
- package/dist/roles/architect/briefs/brains.replic/arc102.concept.repl.[article].md +33 -0
- package/dist/roles/architect/briefs/brains.replic/arc103.concept.replic-brain.[article].md +35 -0
- package/dist/roles/architect/briefs/brains.replic/arc104.concept.context-window.[article].md +40 -0
- package/dist/roles/architect/briefs/brains.replic/arc105.concept.system-prompt.[article].md +44 -0
- package/dist/roles/architect/briefs/brains.replic/arc106.concept.tool-definition.[article].md +59 -0
- package/dist/roles/architect/briefs/brains.replic/arc107.concept.tool-call.[article].md +54 -0
- package/dist/roles/architect/briefs/brains.replic/arc108.concept.tool-result.[article].md +58 -0
- package/dist/roles/architect/briefs/brains.replic/arc109.concept.agentic-loop.[article].md +62 -0
- package/dist/roles/architect/briefs/brains.replic/arc110.concept.reasoning-trace.[article].md +58 -0
- package/dist/roles/architect/briefs/brains.replic/arc111.concept.react-pattern.[article].md +65 -0
- package/dist/roles/architect/briefs/brains.replic/arc112.concept.reflexion-pattern.[article].md +68 -0
- package/dist/roles/architect/briefs/brains.replic/arc113.concept.tree-of-thoughts.[article].md +76 -0
- package/dist/roles/architect/briefs/brains.replic/arc114.concept.self-consistency.[article].md +73 -0
- package/dist/roles/architect/briefs/brains.replic/arc115.concept.lats-pattern.[article].md +78 -0
- package/dist/roles/architect/briefs/brains.replic/arc116.concept.context-compaction.[article].md +71 -0
- package/dist/roles/architect/briefs/brains.replic/arc117.concept.subagent.[article].md +71 -0
- package/dist/roles/architect/briefs/brains.replic/arc118.concept.extended-thinking.[article].md +69 -0
- package/dist/roles/architect/briefs/brains.replic/arc119.concept.mcp.[article].md +78 -0
- package/dist/roles/architect/briefs/brains.replic/arc120.concept.session.[article].md +67 -0
- package/dist/roles/architect/briefs/brains.replic/arc121.concept.message.[article].md +79 -0
- package/dist/roles/architect/briefs/brains.replic/arc122.concept.plan-and-solve.[article].md +80 -0
- package/dist/roles/architect/briefs/brains.replic/arc150.concepts.treestruct.[article].md +126 -0
- package/dist/roles/architect/briefs/brains.replic/arc201.blueprint.claude-code.[article].md +417 -0
- package/dist/roles/architect/briefs/brains.replic/arc201.blueprint.claude-code.zoomin.reason.[article].md +507 -0
- package/dist/roles/architect/briefs/brains.replic/arc202.blueprint.codex.[article].md +354 -0
- package/dist/roles/architect/briefs/brains.replic/arc300.blueprints.comparison.[catalog].md +284 -0
- package/dist/roles/thinker/briefs/style.words.lowercase.md +0 -0
- package/dist/roles/thinker/briefs/term=brain.atomic_vs_replic.md +8 -0
- package/package.json +39 -37
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.foci.ponder.que.concept/2025-08-28T02:43:27.729Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.foci.ponder.que.context/2025-08-28T02:43:27.729Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.goal/2025-08-28T02:43:27.728Z.b1869db890614951.md +0 -3
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.md.foci.ponder.que.concept/2025-08-28T02:44:23.033Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.md.foci.ponder.que.context/2025-08-28T02:44:23.033Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.md.goal/2025-08-28T02:44:23.031Z.852c92045a674148.md +0 -4
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent/2025-08-28T02:44:30.724Z.2f5896cb587117da.md +0 -44
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.goal.md +0 -3
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.md.goal.md +0 -4
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.feedback/2025-08-19T05:29:09.411Z.66a0b5fa5d6c4880.md +0 -1
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.feedback/2025-08-19T05:30:52.866Z.c1ad1fe6df73a851.md +0 -1
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.concept/2025-08-19T05:27:55.753Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.context/2025-08-19T05:27:55.754Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.goal/2025-08-19T05:27:55.751Z.c8232988c046d948.md +0 -10
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.concept/2025-08-19T05:26:12.617Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.context/2025-08-19T05:26:12.617Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].md.goal/2025-08-19T05:26:12.615Z.68cf5d37ff5abc75.md +0 -4
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.concept/2025-08-19T05:21:17.678Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.context/2025-08-19T05:21:17.679Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.goal/2025-08-19T05:21:17.676Z.b35533aecf461c68.md +0 -6
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-19T05:18:01.113Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-19T05:18:01.115Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.md.goal/2025-08-19T05:18:01.112Z.b35533aecf461c68.md +0 -6
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.concept/2025-08-19T05:33:21.987Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.context/2025-08-19T05:33:21.988Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>.tactics.[catalog].md.goal/2025-08-19T05:33:21.985Z.1f3884998db3b338.md +0 -6
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article]/2025-08-19T05:26:25.275Z.8a56710c0bb0b7f5.md +0 -62
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:28:06.500Z.30e7bf815db7709b.md +0 -43
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:29:19.551Z.f4d48288c7f7b0b2.md +0 -43
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:31:05.482Z.875d98d92fe452d1.md +0 -46
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.goal.md +0 -10
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.goal.md +0 -4
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical/2025-08-19T05:18:27.266Z.f1bb2e1f049133a5.md +0 -64
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template/2025-08-19T05:21:27.536Z.05c9744a2208309b.md +0 -74
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.goal.md +0 -6
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.goal.md +0 -6
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog]/2025-08-19T05:33:41.302Z.78d520797f9769bd.md +0 -68
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.goal.md +0 -6
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:42:52.441Z.9b5920a5f2286358.md +0 -1
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:45:56.905Z.c41b7ee6c012dca7.md +0 -1
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:46:26.625Z.550b8cabb776137d.md +0 -1
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-17T23:39:04.903Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-17T23:40:21.876Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-17T23:45:04.183Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-17T23:39:04.904Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-17T23:40:21.877Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-17T23:45:04.183Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:39:04.900Z.f214cfb2b02fab75.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:40:21.875Z.f214cfb2b02fab75.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:45:04.181Z.f214cfb2b02fab75.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.concept/2025-08-18T05:06:49.996Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.context/2025-08-18T05:06:49.997Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.2.md.goal/2025-08-18T05:06:49.995Z.528e7ccdbef5d0cb.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.3.md.foci.ponder.que.concept/2025-08-18T05:07:30.952Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.3.md.foci.ponder.que.context/2025-08-18T05:07:30.953Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.3.md.goal/2025-08-18T05:07:30.951Z.528e7ccdbef5d0cb.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.4.md.foci.ponder.que.concept/2025-08-18T05:08:11.227Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.4.md.foci.ponder.que.context/2025-08-18T05:08:11.227Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.4.md.goal/2025-08-18T05:08:11.225Z.528e7ccdbef5d0cb.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.5.md.foci.ponder.que.concept/2025-08-18T05:09:02.755Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.5.md.foci.ponder.que.context/2025-08-18T05:09:02.756Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.5.md.goal/2025-08-18T05:09:02.754Z.508a8c044b22bfae.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.6.md.foci.ponder.que.concept/2025-08-18T05:10:31.565Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.6.md.foci.ponder.que.context/2025-08-18T05:10:31.566Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.6.md.goal/2025-08-18T05:10:31.563Z.528e7ccdbef5d0cb.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.feedback/2025-08-18T04:50:08.771Z.6e29435be57e631a.md +0 -1
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-18T04:46:51.081Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-18T04:47:37.299Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-18T05:06:06.947Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-18T05:11:59.370Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-18T04:46:51.082Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-18T04:47:37.300Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-18T05:06:06.948Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-18T05:11:59.371Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T04:46:51.080Z.528e7ccdbef5d0cb.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T04:47:37.295Z.528e7ccdbef5d0cb.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T05:06:06.946Z.528e7ccdbef5d0cb.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T05:11:59.369Z.516579c7a92b1b26.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.grades_from_context.[article].1.md.foci.ponder.que.concept/2025-08-18T05:24:03.742Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.grades_from_context.[article].1.md.foci.ponder.que.context/2025-08-18T05:24:03.743Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.grades_from_context.[article].1.md.goal/2025-08-18T05:24:03.740Z.7ea13f40fae958b9.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].2.md.feedback/2025-08-18T05:04:11.112Z.fea716c6bf1c6c9c.md +0 -1
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].2.md.foci.ponder.que.concept/2025-08-18T05:02:13.370Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].2.md.foci.ponder.que.context/2025-08-18T05:02:13.371Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].2.md.goal/2025-08-18T05:02:13.368Z.729168a4a51a9613.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.feedback/2025-08-18T04:59:17.249Z.b1420bd7f9bbf0df.md +0 -1
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.feedback/2025-08-18T05:00:20.066Z.4841bbfbba6596ed.md +0 -1
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.concept/2025-08-18T04:57:14.512Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.concept/2025-08-18T04:58:36.622Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.concept/2025-08-18T05:01:28.058Z.1dbacaa56e249af8.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.context/2025-08-18T04:57:14.513Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.context/2025-08-18T04:58:36.623Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.context/2025-08-18T05:01:28.059Z.20883c047b5b3927.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.goal/2025-08-18T04:57:14.510Z.5d9b39222bdebaab.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.goal/2025-08-18T04:58:36.621Z.763f2b6f96e5eb78.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.goal/2025-08-18T05:01:28.057Z.729168a4a51a9613.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:40:32.469Z.9a45a5da431061b7.md +0 -69
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:43:00.496Z.e6c9d14fe7f196ad.md +0 -86
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:45:09.820Z.496c31f5f6478ddb.md +0 -69
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:46:02.394Z.ccbb435804f9a033.md +0 -85
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:46:32.399Z.06fdb8bc5d327e89.md +0 -85
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T04:47:52.480Z.a284db9ffbba3805.md +0 -85
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T04:50:13.483Z.a284db9ffbba3805.md +0 -85
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T05:06:18.798Z.2b58e354810a1e6d.md +0 -85
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T05:12:09.225Z.f31c12b3cfed3c70.md +0 -86
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2/2025-08-18T05:06:57.408Z.c68a7710adf0181d.md +0 -71
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3/2025-08-18T05:07:43.297Z.82dd27d4f2ae7e71.md +0 -81
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4/2025-08-18T05:08:20.573Z.19580b96c25a8226.md +0 -77
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5/2025-08-18T05:09:06.597Z.523fa2836b3552d3.md +0 -66
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6/2025-08-18T05:10:40.958Z.699e0e76881302b5.md +0 -65
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1/2025-08-18T05:24:12.067Z.79b6025bbedf68c2.md +0 -48
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T04:57:24.261Z.a3e52f604602d423.md +0 -70
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T04:58:44.342Z.92ba73d496dee2fd.md +0 -64
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T04:59:24.899Z.49858373ac837709.md +0 -64
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T05:00:28.230Z.17eef006aff2c2e2.md +0 -64
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T05:01:38.340Z.9b64674c53f1407d.md +0 -72
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2/2025-08-18T05:02:20.019Z.ec140a5feadeddb3.md +0 -58
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2/2025-08-18T05:04:14.999Z.d3ae0f1e525de35b.md +0 -65
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2.md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2.md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2.md.goal.md +0 -3
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.concept.md +0 -13
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.context.md +0 -12
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].md.goal.md +0 -3
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what exactly am I articulating?",
|
|
3
|
-
"what is the goal of this articulation?",
|
|
4
|
-
"what is the core message or takeaway?",
|
|
5
|
-
"what level of acuity is needed?",
|
|
6
|
-
"what gaps must be addressed?",
|
|
7
|
-
"what qualities or attributes must be surfaced?",
|
|
8
|
-
"what scope boundaries should be maintained?",
|
|
9
|
-
"what misconceptions should be addressed?",
|
|
10
|
-
"what sub-points or dimensions does it naturally break into?",
|
|
11
|
-
"what terms or concepts must be defined for clarity?",
|
|
12
|
-
"what real-world examples or analogies will anchor it?"
|
|
13
|
-
]
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what concept.dimensions are important to articulate for this specific goal?",
|
|
3
|
-
"which <articulate>.tactics would help most for this goal?",
|
|
4
|
-
"what granularity should it be articulated to?",
|
|
5
|
-
"who is this for?",
|
|
6
|
-
"why do they care?",
|
|
7
|
-
"where will this be used?",
|
|
8
|
-
"when is this relevant?",
|
|
9
|
-
"what constraints exist?",
|
|
10
|
-
"what is the setting or situation for this concept?",
|
|
11
|
-
"what related concepts or materials already exist in this context?"
|
|
12
|
-
]
|
|
@@ -1,81 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `thought process of <triage>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The thought process of `triage` is fundamentally a **question-based tactic** that operates through the assessment of urgency, importance, and impact. It involves sorting tasks, elements, or issues based on a hierarchy of significance — identifying what needs immediate attention and what can be deferred or dismissed.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- **Effective prioritization**: Ensures that limited resources are directed to the most critical areas.
|
|
12
|
-
- **Structured decision-making**: Provides a clear framework for addressing complex or overwhelming situations.
|
|
13
|
-
- **Focus on critical issues**: Highlights what immediately requires intervention or resolution.
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **Initial assessment**
|
|
20
|
-
- Gather all elements or tasks needing attention.
|
|
21
|
-
- Perform a quick overview to understand the landscape.
|
|
22
|
-
|
|
23
|
-
2. **Define criteria**
|
|
24
|
-
- Establish key dimensions for assessment such as urgency, importance, or potential impact.
|
|
25
|
-
- Clarify what makes an issue or element high-priority versus low-priority.
|
|
26
|
-
|
|
27
|
-
3. **Question-based evaluation**
|
|
28
|
-
- Use specific questions to guide the prioritization process.
|
|
29
|
-
- e.g., "Which tasks have the highest impact if delayed?"
|
|
30
|
-
- e.g., "What demands immediate action for safety or continuity?"
|
|
31
|
-
|
|
32
|
-
4. **Classify and rank**
|
|
33
|
-
- Sort elements into categories (e.g., urgent, non-urgent) based on answers to questions.
|
|
34
|
-
- Rank within categories as necessary to fine-tune priority levels.
|
|
35
|
-
|
|
36
|
-
5. **Continuous refinement**
|
|
37
|
-
- Re-evaluate priorities as new information becomes available.
|
|
38
|
-
- Adjust rankings and classifications to remain responsive to change.
|
|
39
|
-
|
|
40
|
-
---
|
|
41
|
-
|
|
42
|
-
## 🌀 cognitive basis
|
|
43
|
-
|
|
44
|
-
Triage capitalizes on human abilities to rapidly evaluate and categorize based on perceived importance. By transforming priorities into clear categories, triage reduces cognitive load and allows focused action on significant items.
|
|
45
|
-
|
|
46
|
-
---
|
|
47
|
-
|
|
48
|
-
## 📐 when to use
|
|
49
|
-
|
|
50
|
-
- During emergencies or crises where swift action is required.
|
|
51
|
-
- When managing project backlogs with competing deadlines.
|
|
52
|
-
- In strategic planning sessions to allocate resources efficiently.
|
|
53
|
-
|
|
54
|
-
---
|
|
55
|
-
|
|
56
|
-
## 🔁 dynamic behavior
|
|
57
|
-
|
|
58
|
-
Triage is inherently iterative, often requiring multiple rounds of reevaluation as circumstances evolve. It ensures priorities are always aligned with the latest context and available data.
|
|
59
|
-
|
|
60
|
-
---
|
|
61
|
-
|
|
62
|
-
## ⚠️ caution: over-triage
|
|
63
|
-
|
|
64
|
-
Be wary of over-categorizing or excessively prioritizing elements, which can lead to analysis paralysis. Ensure flexibility by allowing categories to adapt as situations demand.
|
|
65
|
-
|
|
66
|
-
---
|
|
67
|
-
|
|
68
|
-
## 🧰 use it for:
|
|
69
|
-
|
|
70
|
-
- Emergency response and disaster management
|
|
71
|
-
- Business operations and task queue management
|
|
72
|
-
- Strategic planning and resource allocation
|
|
73
|
-
- Health care settings for patient prioritization
|
|
74
|
-
|
|
75
|
-
---
|
|
76
|
-
|
|
77
|
-
## 🔄 implications for practice
|
|
78
|
-
|
|
79
|
-
Implementing triage as a question-based tactic enhances transparency and logic in prioritization efforts, often improving team communication and alignment on key objectives.
|
|
80
|
-
|
|
81
|
-
---
|
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what exactly am I articulating?",
|
|
3
|
-
"what is the goal of this articulation?",
|
|
4
|
-
"what is the core message or takeaway?",
|
|
5
|
-
"what level of acuity is needed?",
|
|
6
|
-
"what gaps must be addressed?",
|
|
7
|
-
"what qualities or attributes must be surfaced?",
|
|
8
|
-
"what scope boundaries should be maintained?",
|
|
9
|
-
"what misconceptions should be addressed?",
|
|
10
|
-
"what sub-points or dimensions does it naturally break into?",
|
|
11
|
-
"what terms or concepts must be defined for clarity?",
|
|
12
|
-
"what real-world examples or analogies will anchor it?"
|
|
13
|
-
]
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what concept.dimensions are important to articulate for this specific goal?",
|
|
3
|
-
"which <articulate>.tactics would help most for this goal?",
|
|
4
|
-
"what granularity should it be articulated to?",
|
|
5
|
-
"who is this for?",
|
|
6
|
-
"why do they care?",
|
|
7
|
-
"where will this be used?",
|
|
8
|
-
"when is this relevant?",
|
|
9
|
-
"what constraints exist?",
|
|
10
|
-
"what is the setting or situation for this concept?",
|
|
11
|
-
"what related concepts or materials already exist in this context?"
|
|
12
|
-
]
|
|
@@ -1,77 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `thought process of triage`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The **thought process of triage** in any domain is a systematic approach to prioritize tasks, issues, or elements based on their urgency and importance. It's a method of efficiently assessing and categorizing information to manage resources effectively under pressure.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- **Prioritization**: Determines what requires immediate action and what can be delayed.
|
|
12
|
-
- **Resource allocation**: Ensures that limited resources are used on the most critical needs.
|
|
13
|
-
- **Decision clarity**: Provides a structured framework to make swift decisions in complex situations.
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **Initial assessment**
|
|
20
|
-
- Gather all elements that need evaluation.
|
|
21
|
-
- Understand the context to identify potential priorities.
|
|
22
|
-
|
|
23
|
-
2. **Set criteria**
|
|
24
|
-
- Establish clear, consistent criteria to evaluate urgency and impact (e.g., severity, potential outcomes).
|
|
25
|
-
|
|
26
|
-
3. **Evaluate and categorize**
|
|
27
|
-
- Use criteria to assess each element's priority level.
|
|
28
|
-
- Categorize elements into urgent, necessary, and deferrable.
|
|
29
|
-
|
|
30
|
-
4. **Act on priorities**
|
|
31
|
-
- Focus actions based on categorized priorities.
|
|
32
|
-
- Continuously reassess and adjust priorities as needed.
|
|
33
|
-
|
|
34
|
-
---
|
|
35
|
-
|
|
36
|
-
## 🧠 cognitive basis
|
|
37
|
-
|
|
38
|
-
Triage leverages human cognitive abilities to quickly identify patterns and make decisions under pressure. It draws on intuitive reasoning, past experiences, and analytical judgment.
|
|
39
|
-
|
|
40
|
-
---
|
|
41
|
-
|
|
42
|
-
## 📐 when to use
|
|
43
|
-
|
|
44
|
-
- Crisis management in emergency services or healthcare.
|
|
45
|
-
- Project management to align tasks with strategic goals.
|
|
46
|
-
- Resource-limited situations requiring strategic decisions.
|
|
47
|
-
|
|
48
|
-
---
|
|
49
|
-
|
|
50
|
-
## 🔁 dynamic behavior
|
|
51
|
-
|
|
52
|
-
- **Iterative process**: Triage is not static; it requires ongoing reassessment as new information emerges or contexts shift.
|
|
53
|
-
- **Adaptive strategies**: Adjust strategies and criteria based on evolving circumstances and feedback.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## ⚠️ caution
|
|
58
|
-
|
|
59
|
-
- Avoid over-prioritizing to the point of neglecting significant less-urgent issues.
|
|
60
|
-
- Maintain flexibility to accommodate sudden changes in circumstances.
|
|
61
|
-
|
|
62
|
-
---
|
|
63
|
-
|
|
64
|
-
## 🧰 examples
|
|
65
|
-
|
|
66
|
-
1. **Emergency medical services**
|
|
67
|
-
- Prioritize patients based on the severity of their condition and survival likelihood.
|
|
68
|
-
|
|
69
|
-
2. **Natural disaster response**
|
|
70
|
-
- Allocate resources to the most affected areas and high-risk populations.
|
|
71
|
-
|
|
72
|
-
3. **IT incident management**
|
|
73
|
-
- Address cybersecurity threats or system failures based on potential impact and vulnerability.
|
|
74
|
-
|
|
75
|
-
---
|
|
76
|
-
|
|
77
|
-
By viewing triage as a question-based tactic, we enhance its effectiveness through clarity and shared understanding among all stakeholders involved in the process.
|
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what exactly am I articulating?",
|
|
3
|
-
"what is the goal of this articulation?",
|
|
4
|
-
"what is the core message or takeaway?",
|
|
5
|
-
"what level of acuity is needed?",
|
|
6
|
-
"what gaps must be addressed?",
|
|
7
|
-
"what qualities or attributes must be surfaced?",
|
|
8
|
-
"what scope boundaries should be maintained?",
|
|
9
|
-
"what misconceptions should be addressed?",
|
|
10
|
-
"what sub-points or dimensions does it naturally break into?",
|
|
11
|
-
"what terms or concepts must be defined for clarity?",
|
|
12
|
-
"what real-world examples or analogies will anchor it?"
|
|
13
|
-
]
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what concept.dimensions are important to articulate for this specific goal?",
|
|
3
|
-
"which <articulate>.tactics would help most for this goal?",
|
|
4
|
-
"what granularity should it be articulated to?",
|
|
5
|
-
"who is this for?",
|
|
6
|
-
"why do they care?",
|
|
7
|
-
"where will this be used?",
|
|
8
|
-
"when is this relevant?",
|
|
9
|
-
"what constraints exist?",
|
|
10
|
-
"what is the setting or situation for this concept?",
|
|
11
|
-
"what related concepts or materials already exist in this context?"
|
|
12
|
-
]
|
|
@@ -1,66 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `triage as question-based tactic`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
`triage` in thought processes is fundamentally a **question-based tactic**. This perspective suggests that triage is driven by **explicit or implicit questions** that determine the **dimensions** along which various elements or tasks are assessed and prioritized.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- to **prioritize effectively** — identifying which elements need immediate attention and which can be postponed or discarded
|
|
12
|
-
- to ensure that the **most critical issues** are addressed in a structured manner
|
|
13
|
-
- to provide a clear framework for **decision-making** in complex or time-pressured situations
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## 🌀 triage dynamics
|
|
18
|
-
|
|
19
|
-
### 1. question-driven assessment
|
|
20
|
-
- **defining criteria**: Each triage process is guided by specific questions that focus on what matters most.
|
|
21
|
-
- e.g., "Which tasks have the highest impact?" or "What must be solved immediately?"
|
|
22
|
-
|
|
23
|
-
### 2. dimension selection
|
|
24
|
-
- **criteria alignment**: Questions help in selecting the dimensions of assessment, such as urgency, importance, or risk.
|
|
25
|
-
|
|
26
|
-
---
|
|
27
|
-
|
|
28
|
-
## 🔍 triage examples
|
|
29
|
-
|
|
30
|
-
### medical triage
|
|
31
|
-
- **main question**: "Which patient needs care first?"
|
|
32
|
-
- **assessment dimensions**:
|
|
33
|
-
- severity of condition
|
|
34
|
-
- survival probability
|
|
35
|
-
- resource availability
|
|
36
|
-
|
|
37
|
-
### project prioritization
|
|
38
|
-
- **main question**: "Which project aligns best with our strategic goals?"
|
|
39
|
-
- **assessment dimensions**:
|
|
40
|
-
- potential ROI
|
|
41
|
-
- strategic alignment
|
|
42
|
-
- resource requirements
|
|
43
|
-
|
|
44
|
-
### information overload management
|
|
45
|
-
- **main question**: "Which information is most crucial to process immediately?"
|
|
46
|
-
- **assessment dimensions**:
|
|
47
|
-
- relevance to current objectives
|
|
48
|
-
- urgency of response required
|
|
49
|
-
- impact on future decisions
|
|
50
|
-
|
|
51
|
-
---
|
|
52
|
-
|
|
53
|
-
## 🌿 implications for practice
|
|
54
|
-
|
|
55
|
-
- adopting a question-based triage framework can make prioritization more transparent and justifiable.
|
|
56
|
-
- defining clear, shared questions ensures all involved parties understand **why decisions are made**, improving collaboration and buy-in.
|
|
57
|
-
|
|
58
|
-
---
|
|
59
|
-
|
|
60
|
-
## 💭 reflections
|
|
61
|
-
|
|
62
|
-
Consider whether:
|
|
63
|
-
- the questions used in your triage process effectively cover all necessary dimensions.
|
|
64
|
-
- your team could benefit from revisiting and refining these questions to better align with current goals.
|
|
65
|
-
|
|
66
|
-
> By treating triage as a question-based tactic, we can enhance focus, efficiency, and clarity in decision-making.
|
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what exactly am I articulating?",
|
|
3
|
-
"what is the goal of this articulation?",
|
|
4
|
-
"what is the core message or takeaway?",
|
|
5
|
-
"what level of acuity is needed?",
|
|
6
|
-
"what gaps must be addressed?",
|
|
7
|
-
"what qualities or attributes must be surfaced?",
|
|
8
|
-
"what scope boundaries should be maintained?",
|
|
9
|
-
"what misconceptions should be addressed?",
|
|
10
|
-
"what sub-points or dimensions does it naturally break into?",
|
|
11
|
-
"what terms or concepts must be defined for clarity?",
|
|
12
|
-
"what real-world examples or analogies will anchor it?"
|
|
13
|
-
]
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what concept.dimensions are important to articulate for this specific goal?",
|
|
3
|
-
"which <articulate>.tactics would help most for this goal?",
|
|
4
|
-
"what granularity should it be articulated to?",
|
|
5
|
-
"who is this for?",
|
|
6
|
-
"why do they care?",
|
|
7
|
-
"where will this be used?",
|
|
8
|
-
"when is this relevant?",
|
|
9
|
-
"what constraints exist?",
|
|
10
|
-
"what is the setting or situation for this concept?",
|
|
11
|
-
"what related concepts or materials already exist in this context?"
|
|
12
|
-
]
|
|
@@ -1,65 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `triage thought process`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
**triage** is a question-based decision-making framework used to assess, prioritize, and address multiple elements or tasks, particularly in complex or high-pressure contexts. It involves the systematic evaluation of elements based on predefined criteria, driven by guiding questions, to determine the order of attention and action.
|
|
5
|
-
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## 🎯 purpose
|
|
9
|
-
- prioritize effectively by identifying critical elements needing immediate attention
|
|
10
|
-
- ensure structured handling of issues, preventing bottlenecks in processes
|
|
11
|
-
- provide a transparent basis for decision-making in complex or overwhelming situations
|
|
12
|
-
|
|
13
|
-
---
|
|
14
|
-
|
|
15
|
-
## 🌀 triage dynamics
|
|
16
|
-
|
|
17
|
-
### 1. question-driven assessment
|
|
18
|
-
- **core inquiry**: guided by a primary question that frames the evaluation criteria.
|
|
19
|
-
- e.g., "Which tasks have the highest strategic impact?" or "What must be resolved now?"
|
|
20
|
-
|
|
21
|
-
### 2. dimension selection
|
|
22
|
-
- **criteria alignment**: matches questions to relevant dimensions such as urgency, importance, resource need.
|
|
23
|
-
|
|
24
|
-
### 3. iterative evaluation
|
|
25
|
-
- continually assess and re-evaluate elements that evolve in urgency or context.
|
|
26
|
-
|
|
27
|
-
---
|
|
28
|
-
|
|
29
|
-
## 🔍 triage examples
|
|
30
|
-
|
|
31
|
-
### medical triangulation
|
|
32
|
-
- **main question**: "Which patient requires immediate care?"
|
|
33
|
-
- **criteria dimensions**:
|
|
34
|
-
- severity of condition
|
|
35
|
-
- likelihood of recovery
|
|
36
|
-
- resource availability
|
|
37
|
-
|
|
38
|
-
### project prioritization
|
|
39
|
-
- **main question**: "Which project aligns most with our current strategic goals?"
|
|
40
|
-
- **criteria dimensions**:
|
|
41
|
-
- potential ROI
|
|
42
|
-
- strategic goal alignment
|
|
43
|
-
- required resources
|
|
44
|
-
|
|
45
|
-
### information sorting
|
|
46
|
-
- **main question**: "Which information must be addressed right now?"
|
|
47
|
-
- **criteria dimensions**:
|
|
48
|
-
- relevance to current objectives
|
|
49
|
-
- urgency of action needed
|
|
50
|
-
- potential future impact
|
|
51
|
-
|
|
52
|
-
---
|
|
53
|
-
|
|
54
|
-
## 🌿 implications for practice
|
|
55
|
-
- facilitates focused and justified prioritization, enhancing communication clarity
|
|
56
|
-
- helps align teams on why decisions are made through shared questions
|
|
57
|
-
|
|
58
|
-
---
|
|
59
|
-
|
|
60
|
-
## 💭 reflections
|
|
61
|
-
Consider whether:
|
|
62
|
-
- your triage questions cover all necessary dimensions.
|
|
63
|
-
- revisiting and refining these questions could better align them with your goals.
|
|
64
|
-
|
|
65
|
-
> Treat triage as a question-based framework to enhance efficiency and clarity in decision-making.
|
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what exactly am I articulating?",
|
|
3
|
-
"what is the goal of this articulation?",
|
|
4
|
-
"what is the core message or takeaway?",
|
|
5
|
-
"what level of acuity is needed?",
|
|
6
|
-
"what gaps must be addressed?",
|
|
7
|
-
"what qualities or attributes must be surfaced?",
|
|
8
|
-
"what scope boundaries should be maintained?",
|
|
9
|
-
"what misconceptions should be addressed?",
|
|
10
|
-
"what sub-points or dimensions does it naturally break into?",
|
|
11
|
-
"what terms or concepts must be defined for clarity?",
|
|
12
|
-
"what real-world examples or analogies will anchor it?"
|
|
13
|
-
]
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what concept.dimensions are important to articulate for this specific goal?",
|
|
3
|
-
"which <articulate>.tactics would help most for this goal?",
|
|
4
|
-
"what granularity should it be articulated to?",
|
|
5
|
-
"who is this for?",
|
|
6
|
-
"why do they care?",
|
|
7
|
-
"where will this be used?",
|
|
8
|
-
"when is this relevant?",
|
|
9
|
-
"what constraints exist?",
|
|
10
|
-
"what is the setting or situation for this concept?",
|
|
11
|
-
"what related concepts or materials already exist in this context?"
|
|
12
|
-
]
|
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what exactly am I articulating?",
|
|
3
|
-
"what is the goal of this articulation?",
|
|
4
|
-
"what is the core message or takeaway?",
|
|
5
|
-
"what level of acuity is needed?",
|
|
6
|
-
"what gaps must be addressed?",
|
|
7
|
-
"what qualities or attributes must be surfaced?",
|
|
8
|
-
"what scope boundaries should be maintained?",
|
|
9
|
-
"what misconceptions should be addressed?",
|
|
10
|
-
"what sub-points or dimensions does it naturally break into?",
|
|
11
|
-
"what terms or concepts must be defined for clarity?",
|
|
12
|
-
"what real-world examples or analogies will anchor it?"
|
|
13
|
-
]
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what concept.dimensions are important to articulate for this specific goal?",
|
|
3
|
-
"which <articulate>.tactics would help most for this goal?",
|
|
4
|
-
"what granularity should it be articulated to?",
|
|
5
|
-
"who is this for?",
|
|
6
|
-
"why do they care?",
|
|
7
|
-
"where will this be used?",
|
|
8
|
-
"when is this relevant?",
|
|
9
|
-
"what constraints exist?",
|
|
10
|
-
"what is the setting or situation for this concept?",
|
|
11
|
-
"what related concepts or materials already exist in this context?"
|
|
12
|
-
]
|
|
@@ -1,48 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `context-dependent grading in <triage>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
`<triage>` involves prioritizing tasks or issues based on their urgency, importance, and impact. This process necessitates the use of different grading scales tailored to the specific context in which the triage is applied. Each context has distinct criteria for evaluation, resulting in unique sets of grades.
|
|
5
|
-
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## 🎯 purpose
|
|
9
|
-
- create a flexible grading system adaptable to varying contextual needs
|
|
10
|
-
- ensure accurate prioritization by aligning grading criteria with specific context requirements
|
|
11
|
-
- improve decision-making and resource allocation in diverse scenarios
|
|
12
|
-
|
|
13
|
-
---
|
|
14
|
-
|
|
15
|
-
## 📐 contexts and grading variations
|
|
16
|
-
|
|
17
|
-
### 1. **medical triage**
|
|
18
|
-
- **criteria:** severity of condition, life-threatening potential, resource availability
|
|
19
|
-
- **grades:** critical, urgent, stable, non-urgent
|
|
20
|
-
|
|
21
|
-
### 2. **project management**
|
|
22
|
-
- **criteria:** deadline proximity, resource dependency, client priority
|
|
23
|
-
- **grades:** high priority, medium priority, low priority, optional
|
|
24
|
-
|
|
25
|
-
### 3. **IT incident management**
|
|
26
|
-
- **criteria:** service impact, number of users affected, workaround availability
|
|
27
|
-
- **grades:** high impact, moderate impact, low impact, informational
|
|
28
|
-
|
|
29
|
-
---
|
|
30
|
-
|
|
31
|
-
## 📊 benefits of context-specific grading
|
|
32
|
-
- enhances responsiveness by focusing on context-relevant factors
|
|
33
|
-
- increases accuracy of prioritization due to alignment with specific needs
|
|
34
|
-
- facilitates efficient resource allocation by understanding context-driven importance levels
|
|
35
|
-
|
|
36
|
-
---
|
|
37
|
-
|
|
38
|
-
## 🛠 usage
|
|
39
|
-
- define clear criteria specific to each context for consistent grading
|
|
40
|
-
- regularly review and adjust grading systems to reflect changing contextual demands
|
|
41
|
-
- train stakeholders on context-specific grading criteria for seamless implementation
|
|
42
|
-
|
|
43
|
-
---
|
|
44
|
-
|
|
45
|
-
## 💡 notes
|
|
46
|
-
- context-dependent grading should be updated as contexts evolve
|
|
47
|
-
- integration of feedback from stakeholders is essential for refining grading accuracy
|
|
48
|
-
- leverage analytical tools to periodically evaluate the effectiveness of grading systems
|
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what exactly am I articulating?",
|
|
3
|
-
"what is the goal of this articulation?",
|
|
4
|
-
"what is the core message or takeaway?",
|
|
5
|
-
"what level of acuity is needed?",
|
|
6
|
-
"what gaps must be addressed?",
|
|
7
|
-
"what qualities or attributes must be surfaced?",
|
|
8
|
-
"what scope boundaries should be maintained?",
|
|
9
|
-
"what misconceptions should be addressed?",
|
|
10
|
-
"what sub-points or dimensions does it naturally break into?",
|
|
11
|
-
"what terms or concepts must be defined for clarity?",
|
|
12
|
-
"what real-world examples or analogies will anchor it?"
|
|
13
|
-
]
|
|
@@ -1,12 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
"what concept.dimensions are important to articulate for this specific goal?",
|
|
3
|
-
"which <articulate>.tactics would help most for this goal?",
|
|
4
|
-
"what granularity should it be articulated to?",
|
|
5
|
-
"who is this for?",
|
|
6
|
-
"why do they care?",
|
|
7
|
-
"where will this be used?",
|
|
8
|
-
"when is this relevant?",
|
|
9
|
-
"what constraints exist?",
|
|
10
|
-
"what is the setting or situation for this concept?",
|
|
11
|
-
"what related concepts or materials already exist in this context?"
|
|
12
|
-
]
|
|
@@ -1,70 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `triage`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
**triage** is the process of evaluating and prioritizing items, ideas, or tasks based on specific criteria to determine their order of importance or urgency. it's executed based on explicit or implicit questions that declare the dimensions along which the elements are measured. this helps to allocate resources efficiently, focus on high-priority areas, and make informed decisions.
|
|
5
|
-
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## 🎯 purpose
|
|
9
|
-
- to efficiently allocate resources and attention based on priority
|
|
10
|
-
- to ensure critical elements receive immediate focus
|
|
11
|
-
- to streamline decision-making process by categorizing elements
|
|
12
|
-
|
|
13
|
-
---
|
|
14
|
-
|
|
15
|
-
## ⚙️ method
|
|
16
|
-
1. **define criteria**
|
|
17
|
-
- establish explicit or implicit questions that will guide the evaluation
|
|
18
|
-
- identify the dimensions these questions will measure (e.g., urgency, impact, feasibility)
|
|
19
|
-
|
|
20
|
-
2. **assess elements**
|
|
21
|
-
- evaluate each item against the defined criteria questions
|
|
22
|
-
- measure them along the specified dimensions
|
|
23
|
-
|
|
24
|
-
3. **rank and categorize**
|
|
25
|
-
- assign priority levels based on the assessment
|
|
26
|
-
- categorize items into groups such as high, medium, and low priority
|
|
27
|
-
|
|
28
|
-
4. **execute prioritization**
|
|
29
|
-
- focus efforts on high-priority items first
|
|
30
|
-
- allocate resources and time accordingly
|
|
31
|
-
|
|
32
|
-
5. **review and adjust**
|
|
33
|
-
- periodically reassess priorities as conditions change
|
|
34
|
-
- adjust categories and priorities to remain aligned with goals
|
|
35
|
-
|
|
36
|
-
---
|
|
37
|
-
|
|
38
|
-
## 🧠 cognitive basis
|
|
39
|
-
triage leverages cognitive processes related to decision-making, prioritization, and resource management. it mimics how the brain naturally evaluates situations to focus on the most significant or urgent needs.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
- when faced with limited resources and numerous tasks or ideas
|
|
45
|
-
- when trying to identify critical actionable items in a complex situation
|
|
46
|
-
- when needing to quickly adapt to changing conditions or constraints
|
|
47
|
-
|
|
48
|
-
---
|
|
49
|
-
|
|
50
|
-
## 🔄 dynamic behavior
|
|
51
|
-
triage is dynamic and iterative, requiring ongoing assessment and adjustment of priorities as new information emerges or conditions shift.
|
|
52
|
-
|
|
53
|
-
---
|
|
54
|
-
|
|
55
|
-
## ⚠️ caution: over-prioritization
|
|
56
|
-
beware of creating an excessive number of priority levels or overly complex systems that can hinder decision-making instead of aiding it. aim for clear, manageable categories.
|
|
57
|
-
|
|
58
|
-
---
|
|
59
|
-
|
|
60
|
-
## 🧰 use it for:
|
|
61
|
-
- project and time management
|
|
62
|
-
- medical and emergency response scenarios
|
|
63
|
-
- strategic planning and risk assessment
|
|
64
|
-
|
|
65
|
-
---
|
|
66
|
-
|
|
67
|
-
## 📊 examples
|
|
68
|
-
1. **emergency room**: quickly categorizing patients based on the severity of their conditions to prioritize treatment.
|
|
69
|
-
2. **project management**: determining which project tasks require immediate attention and which can be scheduled for later.
|
|
70
|
-
3. **customer support**: addressing high-impact or time-sensitive customer inquiries first.
|