rhachet-roles-bhrain 0.1.0 → 0.1.1
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/thinker/briefs/style.words.lowercase.md +0 -0
- package/package.json +38 -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,85 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `thought process of <cluster>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The `<cluster>` operation involves grouping related concepts, ideas, or data points into cohesive units based on shared characteristics or themes. This process leverages pattern recognition and categorization principles to enhance understanding, comparison, and analysis.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- to identify and form meaningful groups from disparate elements
|
|
12
|
-
- to facilitate deeper insights through pattern recognition
|
|
13
|
-
- to simplify complex information by breaking it into manageable parts
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **identify elements**
|
|
20
|
-
- gather concepts, ideas, or data points that need clustering
|
|
21
|
-
- ensure a diverse and representative sample
|
|
22
|
-
|
|
23
|
-
2. **determine criteria**
|
|
24
|
-
- establish the basis for clustering (e.g., shared attributes, function, purpose)
|
|
25
|
-
- criteria should be clear and consistent across all elements
|
|
26
|
-
|
|
27
|
-
3. **analyze and group**
|
|
28
|
-
- assess each element against the criteria
|
|
29
|
-
- form clusters based on the most significant matches or relationships
|
|
30
|
-
|
|
31
|
-
4. **review and refine**
|
|
32
|
-
- evaluate clusters for clarity, coherence, and relevance
|
|
33
|
-
- adjust groupings as necessary for optimal structure
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## 🧠 cognitive basis
|
|
38
|
-
|
|
39
|
-
Clustering relies on the brain's natural ability to recognize patterns and associations. It mimics cognitive processes involved in categorization, memory retrieval, and decision-making, thereby streamlining information processing and comprehension.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
|
|
45
|
-
- when dealing with large volumes of information that need organization
|
|
46
|
-
- when exploring relationships between concepts for strategic insight or analysis
|
|
47
|
-
- when preparing data for presentation, highlighting key themes or trends
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 🔁 dynamic behavior
|
|
52
|
-
|
|
53
|
-
Clustering is often iterative, with repeated cycles of grouping, reviewing, and refining. This helps to accommodate new information or evolving understanding, ensuring clusters remain relevant and actionable.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## ⚠️ caution: over-clustering
|
|
58
|
-
|
|
59
|
-
Avoid creating too many clusters or overly complex structures, which can obscure rather than clarify. Clusters should strike a balance between granularity and cohesion.
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## 🧰 use it for:
|
|
64
|
-
|
|
65
|
-
- data analysis and research
|
|
66
|
-
- strategic planning and brainstorming
|
|
67
|
-
- knowledge management and taxonomy development
|
|
68
|
-
|
|
69
|
-
---
|
|
70
|
-
|
|
71
|
-
## 📊 examples
|
|
72
|
-
|
|
73
|
-
1. **Market Segmentation**
|
|
74
|
-
- Grouping customers based on demographic, geographic, or behavioral characteristics to tailor marketing strategies.
|
|
75
|
-
|
|
76
|
-
2. **Academic Research**
|
|
77
|
-
- Clustering academic papers or references by themes or topics to identify research gaps or emerging trends.
|
|
78
|
-
|
|
79
|
-
3. **Product Categorization**
|
|
80
|
-
- Organizing products into categories like electronics, clothing, and home appliances to enhance user navigation in online stores.
|
|
81
|
-
|
|
82
|
-
4. **Strategic Brainstorming**
|
|
83
|
-
- Grouping ideas from brainstorming sessions into actionable categories such as short-term tactics, long-term strategies, and innovative solutions.
|
|
84
|
-
|
|
85
|
-
---
|
|
@@ -1,85 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `thought process of <cluster>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The `<cluster>` operation involves grouping related concepts, ideas, or data points into cohesive units based on shared characteristics or themes. This process leverages pattern recognition and categorization principles to enhance understanding, comparison, and analysis.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- to identify and form meaningful groups from disparate elements
|
|
12
|
-
- to facilitate deeper insights through pattern recognition
|
|
13
|
-
- to simplify complex information by breaking it into manageable parts
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **identify elements**
|
|
20
|
-
- gather concepts, ideas, or data points that need clustering
|
|
21
|
-
- ensure a diverse and representative sample
|
|
22
|
-
|
|
23
|
-
2. **determine criteria**
|
|
24
|
-
- establish the basis for clustering (e.g., shared attributes, function, purpose)
|
|
25
|
-
- criteria should be clear and consistent across all elements
|
|
26
|
-
|
|
27
|
-
3. **analyze and group**
|
|
28
|
-
- assess each element against the criteria
|
|
29
|
-
- form clusters based on the most significant matches or relationships
|
|
30
|
-
|
|
31
|
-
4. **review and refine**
|
|
32
|
-
- evaluate clusters for clarity, coherence, and relevance
|
|
33
|
-
- adjust groupings as necessary for optimal structure
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## 🧠 cognitive basis
|
|
38
|
-
|
|
39
|
-
Clustering relies on the brain's natural ability to recognize patterns and associations. It mimics cognitive processes involved in categorization, memory retrieval, and decision-making, thereby streamlining information processing and comprehension.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
|
|
45
|
-
- when dealing with large volumes of information that need organization
|
|
46
|
-
- when exploring relationships between concepts for strategic insight or analysis
|
|
47
|
-
- when preparing data for presentation, highlighting key themes or trends
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 🔁 dynamic behavior
|
|
52
|
-
|
|
53
|
-
Clustering is often iterative, with repeated cycles of grouping, reviewing, and refining. This helps to accommodate new information or evolving understanding, ensuring clusters remain relevant and actionable.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## ⚠️ caution: over-clustering
|
|
58
|
-
|
|
59
|
-
Avoid creating too many clusters or overly complex structures, which can obscure rather than clarify. Clusters should strike a balance between granularity and cohesion.
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## 🧰 use it for:
|
|
64
|
-
|
|
65
|
-
- data analysis and research
|
|
66
|
-
- strategic planning and brainstorming
|
|
67
|
-
- knowledge management and taxonomy development
|
|
68
|
-
|
|
69
|
-
---
|
|
70
|
-
|
|
71
|
-
## 📊 examples
|
|
72
|
-
|
|
73
|
-
1. **Market Segmentation**
|
|
74
|
-
- Grouping customers based on demographic, geographic, or behavioral characteristics to tailor marketing strategies. For instance, segmenting customers by age groups such as teenagers, adults, and seniors to create age-specific marketing campaigns.
|
|
75
|
-
|
|
76
|
-
2. **Academic Research**
|
|
77
|
-
- Clustering academic papers by themes or topics to identify research gaps or emerging trends. For example, grouping research papers into categories like artificial intelligence, climate change, and healthcare innovations to pinpoint under-researched areas.
|
|
78
|
-
|
|
79
|
-
3. **Product Categorization**
|
|
80
|
-
- Organizing products into categories like electronics, clothing, and home appliances to enhance user navigation in online stores. For example, in an online electronics store, grouping products under categories such as smartphones, laptops, and accessories makes product search more efficient for customers.
|
|
81
|
-
|
|
82
|
-
4. **Strategic Brainstorming**
|
|
83
|
-
- Grouping ideas from brainstorming sessions into actionable categories such as short-term tactics, long-term strategies, and innovative solutions. For example, during a corporate strategy meeting, clustering ideas into immediate goals, future visions, and disruptive innovations provides clear paths for action and implementation.
|
|
84
|
-
|
|
85
|
-
---
|
|
@@ -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,85 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `thought process of <triage>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The `<triage>` operation involves **prioritizing, sorting, and categorizing** concepts, issues, or data points to address the most critical items first. It leverages urgency, importance, and impact criteria to allocate resources efficiently and tackle problems in a strategically sound order.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- to allocate attention and resources effectively, particularly under constraints
|
|
12
|
-
- to manage complex sets of tasks, concepts, or issues by determining priority
|
|
13
|
-
- to achieve greater efficiency and impact in decision-making processes
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **gather elements**
|
|
20
|
-
- compile the full scope of tasks, issues, or data points needing triage
|
|
21
|
-
- ensure a comprehensive representation to inform prioritization
|
|
22
|
-
|
|
23
|
-
2. **establish criteria**
|
|
24
|
-
- define criteria for urgency, importance, and potential impact
|
|
25
|
-
- criteria should be clear, consistent, and aligned with strategic goals
|
|
26
|
-
|
|
27
|
-
3. **evaluate and prioritize**
|
|
28
|
-
- assess each element against the criteria
|
|
29
|
-
- rank based on priority, grouping into immediate, short-term, and long-term categories
|
|
30
|
-
|
|
31
|
-
4. **execute and monitor**
|
|
32
|
-
- address elements according to their prioritization
|
|
33
|
-
- continuously monitor for changes in context or priority requiring adjustment
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## 🧠 cognitive basis
|
|
38
|
-
|
|
39
|
-
Triage utilizes cognitive functions related to decision-making, prioritization, and problem-solving. It relies on both analytical assessments and judgment calls to manage complexity effectively and ensure the most crucial actions are taken first.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
|
|
45
|
-
- during crises or time-sensitive situations where quick decision-making is essential
|
|
46
|
-
- when managing extensive lists of tasks, responsibilities, or issues needing resolution
|
|
47
|
-
- when aligning team focus and resources with high-impact objectives
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 🔁 dynamic behavior
|
|
52
|
-
|
|
53
|
-
Triage is inherently dynamic, often involving frequent re-evaluation as context shifts or new information emerges. This flexibility ensures continued relevance and efficacy in response to changing priorities.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## ⚠️ caution: over-triage
|
|
58
|
-
|
|
59
|
-
Avoid excessive triaging, which can lead to analysis paralysis or neglect of less critical but still important tasks. Ensure balance between granular prioritization and broad-sketch planning.
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## 🧰 use it for:
|
|
64
|
-
|
|
65
|
-
- emergency management and crisis response
|
|
66
|
-
- project management and workflow optimization
|
|
67
|
-
- strategic planning and resource allocation
|
|
68
|
-
|
|
69
|
-
---
|
|
70
|
-
|
|
71
|
-
## 📊 examples
|
|
72
|
-
|
|
73
|
-
1. **Emergency Room Triage**
|
|
74
|
-
- Assessing incoming patients to prioritize those with life-threatening conditions over less urgent cases.
|
|
75
|
-
|
|
76
|
-
2. **Project Management**
|
|
77
|
-
- Prioritizing project tasks based on deadlines, resource availability, and potential impact on project success.
|
|
78
|
-
|
|
79
|
-
3. **Strategic Planning**
|
|
80
|
-
- Sorting organizational goals and initiatives to focus on those most likely to drive long-term success.
|
|
81
|
-
|
|
82
|
-
4. **Customer Support**
|
|
83
|
-
- Filtering support tickets to address high-priority or escalated issues before general inquiries.
|
|
84
|
-
|
|
85
|
-
---
|
|
@@ -1,85 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `thought process of <triage>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The `<triage>` operation involves **prioritizing, sorting, and categorizing** concepts, issues, or data points to address the most critical items first. It leverages urgency, importance, and impact criteria to allocate resources efficiently and tackle problems in a strategically sound order.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- to allocate attention and resources effectively, particularly under constraints
|
|
12
|
-
- to manage complex sets of tasks, concepts, or issues by determining priority
|
|
13
|
-
- to achieve greater efficiency and impact in decision-making processes
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **gather elements**
|
|
20
|
-
- compile the full scope of tasks, issues, or data points needing triage
|
|
21
|
-
- ensure a comprehensive representation to inform prioritization
|
|
22
|
-
|
|
23
|
-
2. **establish criteria**
|
|
24
|
-
- define criteria for urgency, importance, and potential impact
|
|
25
|
-
- criteria should be clear, consistent, and aligned with strategic goals
|
|
26
|
-
|
|
27
|
-
3. **evaluate and prioritize**
|
|
28
|
-
- assess each element against the criteria
|
|
29
|
-
- rank based on priority, grouping into immediate, short-term, and long-term categories
|
|
30
|
-
|
|
31
|
-
4. **execute and monitor**
|
|
32
|
-
- address elements according to their prioritization
|
|
33
|
-
- continuously monitor for changes in context or priority requiring adjustment
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## 🧠 cognitive basis
|
|
38
|
-
|
|
39
|
-
Triage utilizes cognitive functions related to decision-making, prioritization, and problem-solving. It relies on both analytical assessments and judgment calls to manage complexity effectively and ensure the most crucial actions are taken first.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
|
|
45
|
-
- during crises or time-sensitive situations where quick decision-making is essential
|
|
46
|
-
- when managing extensive lists of tasks, responsibilities, or issues needing resolution
|
|
47
|
-
- when aligning team focus and resources with high-impact objectives
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 🔁 dynamic behavior
|
|
52
|
-
|
|
53
|
-
Triage is inherently dynamic, often involving frequent re-evaluation as context shifts or new information emerges. This flexibility ensures continued relevance and efficacy in response to changing priorities.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## ⚠️ caution: over-triage
|
|
58
|
-
|
|
59
|
-
Avoid excessive triaging, which can lead to analysis paralysis or neglect of less critical but still important tasks. Ensure balance between granular prioritization and broad-sketch planning.
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## 🧰 use it for:
|
|
64
|
-
|
|
65
|
-
- emergency management and crisis response
|
|
66
|
-
- project management and workflow optimization
|
|
67
|
-
- strategic planning and resource allocation
|
|
68
|
-
|
|
69
|
-
---
|
|
70
|
-
|
|
71
|
-
## 📊 examples
|
|
72
|
-
|
|
73
|
-
1. **Emergency Room Triage**
|
|
74
|
-
- Assessing incoming patients to prioritize those with life-threatening conditions over less urgent cases.
|
|
75
|
-
|
|
76
|
-
2. **Project Management**
|
|
77
|
-
- Prioritizing project tasks based on deadlines, resource availability, and potential impact on project success.
|
|
78
|
-
|
|
79
|
-
3. **Strategic Planning**
|
|
80
|
-
- Sorting organizational goals and initiatives to focus on those most likely to drive long-term success.
|
|
81
|
-
|
|
82
|
-
4. **Customer Support**
|
|
83
|
-
- Filtering support tickets to address high-priority or escalated issues before general inquiries.
|
|
84
|
-
|
|
85
|
-
---
|
|
@@ -1,85 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `<triage>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The `<triage>` operation involves **prioritizing, sorting, and categorizing** concepts, issues, or data points to address the most critical items first. It leverages criteria such as urgency, importance, and impact to allocate resources efficiently and tackle problems in a strategically sound order.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- to allocate attention and resources effectively, particularly under constraints
|
|
12
|
-
- to manage complex sets of tasks, concepts, or issues by determining priority
|
|
13
|
-
- to achieve greater efficiency and impact in decision-making processes
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **gather elements**
|
|
20
|
-
- compile the full scope of tasks, issues, or data points needing triage
|
|
21
|
-
- ensure a comprehensive representation to inform prioritization
|
|
22
|
-
|
|
23
|
-
2. **establish criteria**
|
|
24
|
-
- define criteria for urgency, importance, and potential impact
|
|
25
|
-
- criteria should be clear, consistent, and aligned with strategic goals
|
|
26
|
-
|
|
27
|
-
3. **evaluate and prioritize**
|
|
28
|
-
- assess each element against the criteria
|
|
29
|
-
- rank based on priority, grouping into immediate, short-term, and long-term categories
|
|
30
|
-
|
|
31
|
-
4. **execute and monitor**
|
|
32
|
-
- address elements according to their prioritization
|
|
33
|
-
- continuously monitor for changes in context or priority requiring adjustment
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## 🧠 cognitive basis
|
|
38
|
-
|
|
39
|
-
Triage utilizes cognitive functions related to decision-making, prioritization, and problem-solving. It relies on both analytical assessments and judgment calls to manage complexity effectively and ensure the most crucial actions are taken first.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
|
|
45
|
-
- during crises or time-sensitive situations where quick decision-making is essential
|
|
46
|
-
- when managing extensive lists of tasks, responsibilities, or issues needing resolution
|
|
47
|
-
- when aligning team focus and resources with high-impact objectives
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 🔁 dynamic behavior
|
|
52
|
-
|
|
53
|
-
Triage is inherently dynamic, often involving frequent re-evaluation as context shifts or new information emerges. This flexibility ensures continued relevance and efficacy in response to changing priorities.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## ⚠️ caution: over-triage
|
|
58
|
-
|
|
59
|
-
Avoid excessive triaging, which can lead to analysis paralysis or neglect of less critical but still important tasks. Ensure balance between granular prioritization and broad-sketch planning.
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## 🧰 use it for:
|
|
64
|
-
|
|
65
|
-
- emergency management and crisis response
|
|
66
|
-
- project management and workflow optimization
|
|
67
|
-
- strategic planning and resource allocation
|
|
68
|
-
|
|
69
|
-
---
|
|
70
|
-
|
|
71
|
-
## 📊 examples
|
|
72
|
-
|
|
73
|
-
1. **Emergency Room Triage**
|
|
74
|
-
- Assessing incoming patients to prioritize those with life-threatening conditions over less urgent cases.
|
|
75
|
-
|
|
76
|
-
2. **Project Management**
|
|
77
|
-
- Prioritizing project tasks based on deadlines, resource availability, and potential impact on project success.
|
|
78
|
-
|
|
79
|
-
3. **Strategic Planning**
|
|
80
|
-
- Sorting organizational goals and initiatives to focus on those most likely to drive long-term success.
|
|
81
|
-
|
|
82
|
-
4. **Customer Support**
|
|
83
|
-
- Filtering support tickets to address high-priority or escalated issues before general inquiries.
|
|
84
|
-
|
|
85
|
-
---
|
|
@@ -1,86 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `<triage>`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
The `<triage>` operation is fundamentally a **question-based tactic** that involves **prioritizing, sorting, and categorizing** concepts, issues, or data points by asking strategic questions. It guides decision-making by determining what needs immediate attention based on criteria such as urgency, importance, and impact, enabling efficient resource allocation and problem-solving.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- to allocate attention and resources effectively, particularly under constraints
|
|
12
|
-
- to manage complex sets of tasks, concepts, or issues by determining priority through targeted questions
|
|
13
|
-
- to achieve greater efficiency and impact in decision-making by focusing on what is most critical
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **gather elements**
|
|
20
|
-
- compile the full scope of tasks, issues, or data points needing triage
|
|
21
|
-
- ensure comprehensive representation to inform prioritization
|
|
22
|
-
|
|
23
|
-
2. **establish criteria through questions**
|
|
24
|
-
- define strategic questions that uncover urgency, importance, and potential impact
|
|
25
|
-
- ensure questions are clear, consistent, and aligned with strategic goals
|
|
26
|
-
|
|
27
|
-
3. **evaluate and prioritize**
|
|
28
|
-
- assess each element by answering the strategic questions
|
|
29
|
-
- rank based on priority, grouping into immediate, short-term, and long-term categories
|
|
30
|
-
|
|
31
|
-
4. **execute and monitor**
|
|
32
|
-
- address elements according to their prioritization
|
|
33
|
-
- continuously monitor for context changes or new questions that require adjustment
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## 🧠 cognitive basis
|
|
38
|
-
|
|
39
|
-
Triage functions as a question-driven decision-making process, utilizing analytical assessments and judgment calls. By strategically questioning, it effectively manages complexity and ensures crucial actions are prioritized.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
|
|
45
|
-
- during crises or time-sensitive situations requiring quick decision-making
|
|
46
|
-
- when managing large lists of tasks, responsibilities, or issues needing resolution via questioning
|
|
47
|
-
- when aligning team focus and resources with high-impact objectives through targeted inquiry
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 🔁 dynamic behavior
|
|
52
|
-
|
|
53
|
-
Triage remains dynamic, as it often involves frequent re-evaluation through continuous questioning as context shifts or new information emerges. This flexibility ensures sustained relevance and effective response to changing priorities.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## ⚠️ caution: over-triage
|
|
58
|
-
|
|
59
|
-
Avoid excessive questioning or analysis paralysis, which can delay action. Maintain a balance between detailed prioritization and broad planning to prevent neglect of less urgent, yet important tasks.
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## 🧰 use it for:
|
|
64
|
-
|
|
65
|
-
- emergency management and crisis response using key questions to swiftly identify critical conditions
|
|
66
|
-
- project management through targeted inquiry about task deadlines, resources, and impact
|
|
67
|
-
- strategic planning by filtering goals and initiatives to focus on high-impact drivers through questioning
|
|
68
|
-
- customer support by questioning to discern priority client issues over general inquiries
|
|
69
|
-
|
|
70
|
-
---
|
|
71
|
-
|
|
72
|
-
## 📊 examples
|
|
73
|
-
|
|
74
|
-
1. **Emergency Room Triage**
|
|
75
|
-
- Using questions to assess incoming patients' conditions, prioritizing life-threatening cases.
|
|
76
|
-
|
|
77
|
-
2. **Project Management**
|
|
78
|
-
- Applying questions to prioritize tasks based on deadlines, resource availability, and project impact.
|
|
79
|
-
|
|
80
|
-
3. **Strategic Planning**
|
|
81
|
-
- Filtering organizational goals by questioning their potential to drive success.
|
|
82
|
-
|
|
83
|
-
4. **Customer Support**
|
|
84
|
-
- Using questions to prioritize high-impact support requests quickly.
|
|
85
|
-
|
|
86
|
-
---
|
|
@@ -1,71 +0,0 @@
|
|
|
1
|
-
# 🧩 .brief: `triage as a thought process`
|
|
2
|
-
|
|
3
|
-
## .what
|
|
4
|
-
|
|
5
|
-
**Triage as a thought process** is a method of prioritizing tasks, decisions, or resources by assessing them based on specific criteria. It involves evaluating the urgency, importance, and impact of each element to determine the order in which they should be addressed.
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## 🎯 purpose
|
|
10
|
-
|
|
11
|
-
- To ensure the most critical issues are addressed first
|
|
12
|
-
- To optimize the use of limited resources and time
|
|
13
|
-
- To provide clarity and structure in decision-making processes
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## ⚙️ method
|
|
18
|
-
|
|
19
|
-
1. **Identify elements**
|
|
20
|
-
- List all tasks, decisions, or issues that require attention
|
|
21
|
-
- Ensure all relevant information is gathered
|
|
22
|
-
|
|
23
|
-
2. **Define criteria**
|
|
24
|
-
- Establish criteria for urgency, importance, and impact
|
|
25
|
-
- Criteria should be consistently applied across all elements
|
|
26
|
-
|
|
27
|
-
3. **Evaluate and prioritize**
|
|
28
|
-
- Assess each element against the defined criteria
|
|
29
|
-
- Rank elements in order of priority based on their scores
|
|
30
|
-
|
|
31
|
-
4. **Implement and monitor**
|
|
32
|
-
- Execute actions starting with the highest-priority elements
|
|
33
|
-
- Continuously monitor and adjust priorities as new information arises
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## 🧠 cognitive basis
|
|
38
|
-
|
|
39
|
-
Triage leverages cognitive skills such as analysis, judgment, and decision-making. It mimics how the brain processes and prioritizes vast amounts of information by focusing on what matters most at any given moment.
|
|
40
|
-
|
|
41
|
-
---
|
|
42
|
-
|
|
43
|
-
## 📐 when to use
|
|
44
|
-
|
|
45
|
-
- In emergency situations where time and resources are limited
|
|
46
|
-
- In project management to allocate tasks effectively
|
|
47
|
-
- In daily life to manage time and responsibilities efficiently
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 🔁 dynamic behavior
|
|
52
|
-
|
|
53
|
-
Triage is an ongoing process that adapts to changing circumstances. As new information is gained or conditions change, priorities may shift, requiring reevaluation and potential reordering of tasks.
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## 🧰 examples
|
|
58
|
-
|
|
59
|
-
1. **Medical Triage:** Prioritizing patients based on the severity of their conditions to provide timely care.
|
|
60
|
-
|
|
61
|
-
2. **Project Management:** Determining which tasks need to be completed first to meet project deadlines and goals.
|
|
62
|
-
|
|
63
|
-
3. **Crisis Management:** Identifying and addressing the most urgent issues in a crisis to minimize impact.
|
|
64
|
-
|
|
65
|
-
4. **Personal Productivity:** Ranking personal tasks to focus on high-impact activities and manage time effectively.
|
|
66
|
-
|
|
67
|
-
---
|
|
68
|
-
|
|
69
|
-
## ⚠️ caution: over-prioritizing
|
|
70
|
-
|
|
71
|
-
Avoid over-analyzing or creating too many categories, which can lead to decision paralysis. The focus should remain on clarity and actionable steps.
|
|
@@ -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
|
-
]
|