rhachet-roles-bhrain 0.1.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/.test/genContextLogTrail.d.ts +2 -0
- package/dist/.test/genContextLogTrail.js +12 -0
- package/dist/.test/genContextLogTrail.js.map +1 -0
- package/dist/.test/genContextStitchTrail.d.ts +1 -0
- package/dist/.test/genContextStitchTrail.js +6 -0
- package/dist/.test/genContextStitchTrail.js.map +1 -0
- package/dist/.test/getContextOpenAI.d.ts +2 -0
- package/dist/.test/getContextOpenAI.js +19 -0
- package/dist/.test/getContextOpenAI.js.map +1 -0
- package/dist/_topublish/domain-glossary-brief/src/domain/objects/Catalog.d.ts +0 -0
- package/dist/_topublish/domain-glossary-brief/src/domain/objects/Catalog.js +2 -0
- package/dist/_topublish/domain-glossary-brief/src/domain/objects/Catalog.js.map +1 -0
- package/dist/_topublish/domain-glossary-brief/src/domain/objects/TriageCatalog.d.ts +18 -0
- package/dist/_topublish/domain-glossary-brief/src/domain/objects/TriageCatalog.js +3 -0
- package/dist/_topublish/domain-glossary-brief/src/domain/objects/TriageCatalog.js.map +1 -0
- package/dist/_topublish/rhachet-roles-bhrain/src/domain/objects/Focus.d.ts +34 -0
- package/dist/_topublish/rhachet-roles-bhrain/src/domain/objects/Focus.js +9 -0
- package/dist/_topublish/rhachet-roles-bhrain/src/domain/objects/Focus.js.map +1 -0
- package/dist/_topublish/rhachet-roles-bhrain/src/domain/objects/Question.d.ts +1 -0
- package/dist/_topublish/rhachet-roles-bhrain/src/domain/objects/Question.js +3 -0
- package/dist/_topublish/rhachet-roles-bhrain/src/domain/objects/Question.js.map +1 -0
- package/dist/access/sdk/sdkOpenAi.d.ts +16 -0
- package/dist/access/sdk/sdkOpenAi.js +42 -0
- package/dist/access/sdk/sdkOpenAi.js.map +1 -0
- package/dist/contract/commands/codegenBriefOptions.d.ts +1 -0
- package/dist/contract/commands/codegenBriefOptions.js +54 -0
- package/dist/contract/commands/codegenBriefOptions.js.map +1 -0
- package/dist/contract/sdk/index.d.ts +2 -0
- package/dist/contract/sdk/index.js +8 -0
- package/dist/contract/sdk/index.js.map +1 -0
- package/dist/domain.operations/artifact/asDotRhachetFile.d.ts +5 -0
- package/dist/domain.operations/artifact/asDotRhachetFile.js +16 -0
- package/dist/domain.operations/artifact/asDotRhachetFile.js.map +1 -0
- package/dist/domain.operations/artifact/genLoopFeedback.d.ts +18 -0
- package/dist/domain.operations/artifact/genLoopFeedback.js +40 -0
- package/dist/domain.operations/artifact/genLoopFeedback.js.map +1 -0
- package/dist/domain.operations/artifact/genStepArtDel.d.ts +17 -0
- package/dist/domain.operations/artifact/genStepArtDel.js +29 -0
- package/dist/domain.operations/artifact/genStepArtDel.js.map +1 -0
- package/dist/domain.operations/artifact/genStepArtSet.d.ts +14 -0
- package/dist/domain.operations/artifact/genStepArtSet.js +49 -0
- package/dist/domain.operations/artifact/genStepArtSet.js.map +1 -0
- package/dist/domain.operations/artifact/genStepGrabCallerFeedbackToArtifact.d.ts +19 -0
- package/dist/domain.operations/artifact/genStepGrabCallerFeedbackToArtifact.js +100 -0
- package/dist/domain.operations/artifact/genStepGrabCallerFeedbackToArtifact.js.map +1 -0
- package/dist/domain.operations/artifact/genStepResetFeedback.d.ts +12 -0
- package/dist/domain.operations/artifact/genStepResetFeedback.js +27 -0
- package/dist/domain.operations/artifact/genStepResetFeedback.js.map +1 -0
- package/dist/domain.operations/artifact/genStepSwapArtifact.d.ts +57 -0
- package/dist/domain.operations/artifact/genStepSwapArtifact.js +58 -0
- package/dist/domain.operations/artifact/genStepSwapArtifact.js.map +1 -0
- package/dist/domain.operations/artifact/setSkillOutputSrc.d.ts +32 -0
- package/dist/domain.operations/artifact/setSkillOutputSrc.js +99 -0
- package/dist/domain.operations/artifact/setSkillOutputSrc.js.map +1 -0
- package/dist/domain.operations/context/genStitchStreamToDisk.d.ts +13 -0
- package/dist/domain.operations/context/genStitchStreamToDisk.js +74 -0
- package/dist/domain.operations/context/genStitchStreamToDisk.js.map +1 -0
- package/dist/domain.operations/hooks/decodeDocOutputPath.d.ts +21 -0
- package/dist/domain.operations/hooks/decodeDocOutputPath.js +57 -0
- package/dist/domain.operations/hooks/decodeDocOutputPath.js.map +1 -0
- package/dist/domain.operations/hooks/execTranslateDocOutputPath.d.ts +20 -0
- package/dist/domain.operations/hooks/execTranslateDocOutputPath.js +80 -0
- package/dist/domain.operations/hooks/execTranslateDocOutputPath.js.map +1 -0
- package/dist/domain.operations/hooks/getInvokeHooks.d.ts +2 -0
- package/dist/domain.operations/hooks/getInvokeHooks.js +15 -0
- package/dist/domain.operations/hooks/getInvokeHooks.js.map +1 -0
- package/dist/domain.operations/hooks/relateDocOutputPath.d.ts +11 -0
- package/dist/domain.operations/hooks/relateDocOutputPath.js +58 -0
- package/dist/domain.operations/hooks/relateDocOutputPath.js.map +1 -0
- package/dist/index.d.ts +1 -0
- package/dist/index.js +18 -0
- package/dist/index.js.map +1 -0
- package/dist/roles/getRoleRegistry.d.ts +8 -0
- package/dist/roles/getRoleRegistry.js +19 -0
- package/dist/roles/getRoleRegistry.js.map +1 -0
- package/dist/roles/getRoleRegistry.readme.d.ts +1 -0
- package/dist/roles/getRoleRegistry.readme.js +22 -0
- package/dist/roles/getRoleRegistry.readme.js.map +1 -0
- package/dist/roles/thinker/briefs/cognition/cog000.overview.and.premise.md +115 -0
- package/dist/roles/thinker/briefs/cognition/cog021.coordinates.spherical.md +69 -0
- package/dist/roles/thinker/briefs/cognition/cog021.metaphor.cauliflorous.md +44 -0
- package/dist/roles/thinker/briefs/cognition/cog021.metaphor.galactic_spacetravel.[article].md +42 -0
- package/dist/roles/thinker/briefs/cognition/cog021.metaphor.galactic_spacetravel.[lesson].md +60 -0
- package/dist/roles/thinker/briefs/cognition/cog021.structs.catalog.md +51 -0
- package/dist/roles/thinker/briefs/cognition/cog021.structs.treestruct.md +85 -0
- package/dist/roles/thinker/briefs/cognition/cog021.structs.vector.md +112 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.definition.md +115 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct._.md +112 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct.coords.1.spherical.md +80 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct.coords.2.abstractive.md +59 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct.coords.3.descriptive.md +64 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct.persp.1.perspectives.md +88 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct.persp.2.universal.md +82 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct.persp.3.relative.md +106 -0
- package/dist/roles/thinker/briefs/cognition/cog101.concept.treestruct.persp.4.fractal.md +83 -0
- package/dist/roles/thinker/briefs/cognition/cog151.concept.treestruct.gravity.md +89 -0
- package/dist/roles/thinker/briefs/cognition/cog201.cortal.focus.p1.definition.md +231 -0
- package/dist/roles/thinker/briefs/cognition/cog201.cortal.focus.p1.examples.cont.md +82 -0
- package/dist/roles/thinker/briefs/cognition/cog201.cortal.focus.p2.acuity.md +134 -0
- package/dist/roles/thinker/briefs/cognition/cog201.cortal.focus.p2.breadth.md +151 -0
- package/dist/roles/thinker/briefs/cognition/cog201.cortal.focus.p2.depth.md +147 -0
- package/dist/roles/thinker/briefs/cognition/cog251.cortal.focus.p3.fabric.md +96 -0
- package/dist/roles/thinker/briefs/cognition/cog251.cortal.focus.p3.mode.md +68 -0
- package/dist/roles/thinker/briefs/cognition/cog251.cortal.focus.p3.rythm.md +56 -0
- package/dist/roles/thinker/briefs/cognition/cog251.cortal.focus.p3.usecases.md +76 -0
- package/dist/roles/thinker/briefs/cognition/cog301.traversal.1.motion.primitives._.md +155 -0
- package/dist/roles/thinker/briefs/cognition/cog301.traversal.1.motion.primitives.acuity.md +94 -0
- package/dist/roles/thinker/briefs/cognition/cog301.traversal.1.motion.primitives.breadth.md +114 -0
- package/dist/roles/thinker/briefs/cognition/cog301.traversal.1.motion.primitives.breadth.vary.md +105 -0
- package/dist/roles/thinker/briefs/cognition/cog301.traversal.1.motion.primitives.depth.md +132 -0
- package/dist/roles/thinker/briefs/cognition/cog301.traversal.2.motion.composites._.md +106 -0
- package/dist/roles/thinker/briefs/cognition/cog301.traversal.2.motion.composites.grammar.md +105 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.._.md +209 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.1.persp.as.berries.md +168 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.1.persp.as.vectors.md +74 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.1.persp.has.precision.tunable.md +80 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.2.1.primitives.rough._.md +99 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.2.1.primitives.rough.interrogative.md +108 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.2.1.primitives.rough.why.[article].md +55 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.2.2.composite.smooth._.md +83 -0
- package/dist/roles/thinker/briefs/cognition/cog401.questions.2.2.composite.smooth.examples.md +101 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang.1.primitives._.md +134 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang.1.primitives.recall.md +149 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang.1.primitives.steer.md +146 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang.1.primitives.think.md +141 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang.2.composites.zoom.md +127 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang.3.catalogs.md +107 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang.3.grammar.md +124 -0
- package/dist/roles/thinker/briefs/cognition/cog501.cortal.assemblylang_.md +0 -0
- package/dist/roles/thinker/briefs/cognition/inflight/concept.vs.idea.md +70 -0
- package/dist/roles/thinker/briefs/cognition/inflight/core.concept.adjectives.md +8 -0
- package/dist/roles/thinker/briefs/distilisys.grammar.compressed.md +19 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.1.why.common.[article].md +32 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.1.why.term_smells.[article].md +36 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.1.why.term_smells.detection.[lesson].md +73 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.2.tactic.eliminate.[article].md +55 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.2.tactic.eliminate.[lesson].md +41 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.3.eliminator.[trait]._.md +66 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.3.eliminator.[trait].balance.md +36 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.3.eliminator.[trait].bane.md +34 -0
- package/dist/roles/thinker/briefs/grammar/gerunds.3.eliminator.[trait].boon.md +35 -0
- package/dist/roles/thinker/briefs/knowledge/kno101.primitives.1.ontology.[article].frame.docs_as_materializations.md +63 -0
- package/dist/roles/thinker/briefs/knowledge/kno101.primitives.1.ontology.[article].frame.docs_as_references.md +45 -0
- package/dist/roles/thinker/briefs/knowledge/kno101.primitives.2.rel.many_to_many.[article].md +37 -0
- package/dist/roles/thinker/briefs/knowledge/kno101.primitives.3.instances.[article].md +39 -0
- package/dist/roles/thinker/briefs/knowledge/kno101.primitives.4.documents.[article].md +37 -0
- package/dist/roles/thinker/briefs/knowledge/kno101.primitives.5.concepts.[article].md +39 -0
- package/dist/roles/thinker/briefs/knowledge/kno201.documents._.[article].md +48 -0
- package/dist/roles/thinker/briefs/knowledge/kno201.documents._.[catalog].md +52 -0
- package/dist/roles/thinker/briefs/knowledge/kno201.documents.articles.[article].md +40 -0
- package/dist/roles/thinker/briefs/knowledge/kno201.documents.catalogs.[article].md +41 -0
- package/dist/roles/thinker/briefs/knowledge/kno201.documents.demos.[article].md +42 -0
- package/dist/roles/thinker/briefs/knowledge/kno201.documents.lessons.[article].md +42 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.compression.1.refs._.[article].md +41 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.compression.2.kernels._.[article].i1.md +50 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.compression.3.briefs._.[article].md +40 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.compression._.[article].md +90 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.compression._.[catalog].persp.garden.md +64 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[article].md +45 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].algorithm.md +54 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].color.md +56 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].empathy.md +54 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].entropy.md +54 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].gravity.md +54 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].joke.md +56 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].value.md +54 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2._.[catalog].md +43 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.articulate.[article].md +27 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.articulate.[lesson].md +49 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.catalogize.[article].md +27 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.catalogize.[lesson].md +54 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.demonstrate.[article].md +26 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.demonstrate.[lesson].md +49 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.lessonize.[article].md +26 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.enbrief.2.lessonize.[lesson].md +54 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.kernelize._.[article].md +58 -0
- package/dist/roles/thinker/briefs/knowledge/kno301.doc.kernelize._.[lesson].md +88 -0
- package/dist/roles/thinker/briefs/knowledge/kno351.docs.are_instances.[article].md +34 -0
- package/dist/roles/thinker/briefs/knowledge/kno351.docs.recursion.[catalog].md +44 -0
- package/dist/roles/thinker/briefs/knowledge/kno401.actors.1.role.author.[article].md +36 -0
- package/dist/roles/thinker/briefs/knowledge/kno401.actors.1.role.librarian.[article].md +40 -0
- package/dist/roles/thinker/briefs/knowledge/kno401.actors.2.interdependence.[article].md +52 -0
- package/dist/roles/thinker/briefs/knowledge/kno501.doc.enbrief.catalog.structure1.[article].md +53 -0
- package/dist/roles/thinker/briefs/knowledge/kno501.doc.enbrief.catalog.structure1.[lesson].template.md +101 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.foci.ponder.que.concept/2025-08-28T02:43:27.729Z.1dbacaa56e249af8.md +13 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.foci.ponder.que.context/2025-08-28T02:43:27.729Z.20883c047b5b3927.md +12 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.goal/2025-08-28T02:43:27.728Z.b1869db890614951.md +3 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.md.foci.ponder.que.concept/2025-08-28T02:44:23.033Z.1dbacaa56e249af8.md +13 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.md.foci.ponder.que.context/2025-08-28T02:44:23.033Z.20883c047b5b3927.md +12 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.md.goal/2025-08-28T02:44:23.031Z.852c92045a674148.md +4 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent/2025-08-28T02:44:30.724Z.2f5896cb587117da.md +44 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.goal.md +3 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.md.goal.md +4 -0
- package/dist/roles/thinker/briefs/librarian.context/article.variant.vision.[article].md +60 -0
- package/dist/roles/thinker/briefs/librarian.context/term.expectation.vs_assumption._.md +60 -0
- package/dist/roles/thinker/briefs/librarian.context/term.frame.vs_perspective.[article].md +96 -0
- package/dist/roles/thinker/briefs/librarian.context/term.invariant.[article].md +29 -0
- package/dist/roles/thinker/briefs/librarian.context/term.lesson._vs_article.[article].md +36 -0
- package/dist/roles/thinker/briefs/librarian.context/term.ref._vs_brief.md +90 -0
- package/dist/roles/thinker/briefs/librarian.context/term.referent.[article].md +43 -0
- package/dist/roles/thinker/briefs/librarian.context/usage.lesson_vs_article.[lesson].md +31 -0
- package/dist/roles/thinker/briefs/librarian.context/usage.lesson_vs_article_vs_demo.[lesson].md +37 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.readme.md +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.feedback/2025-08-19T05:29:09.411Z.66a0b5fa5d6c4880.md +1 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.feedback/2025-08-19T05:30:52.866Z.c1ad1fe6df73a851.md +1 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.goal/2025-08-19T05:27:55.751Z.c8232988c046d948.md +10 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].md.goal/2025-08-19T05:26:12.615Z.68cf5d37ff5abc75.md +4 -0
- 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 +13 -0
- 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 +12 -0
- 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 +6 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.md.goal/2025-08-19T05:18:01.112Z.b35533aecf461c68.md +6 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>.tactics.[catalog].md.goal/2025-08-19T05:33:21.985Z.1f3884998db3b338.md +6 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article]/2025-08-19T05:26:25.275Z.8a56710c0bb0b7f5.md +62 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:28:06.500Z.30e7bf815db7709b.md +43 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:29:19.551Z.f4d48288c7f7b0b2.md +43 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:31:05.482Z.875d98d92fe452d1.md +46 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.goal.md +10 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.goal.md +4 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical/2025-08-19T05:18:27.266Z.f1bb2e1f049133a5.md +64 -0
- 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 +74 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.goal.md +6 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.goal.md +6 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog]/2025-08-19T05:33:41.302Z.78d520797f9769bd.md +68 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.goal.md +6 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>._.[article].frame.cognitive.md +33 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>._.[article].frame.tactical.md +45 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tactic.[catalog].md +83 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tactic.concept_dimension.examples.[article][seed].md +4 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tactic.concept_dimension.invariants.[article].md +36 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tactic.from.examples.md +44 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tactic.from.seed.md +48 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tactic.with.templates.[article].md +57 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tactic.with.templates.[gallery][review].effective.md +1 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<articulate>.tone.bluecollar.[article][seed].md +5 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<catalogize>._.[article][seed].md +3 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<catalogize>.observation.via_clusterage_over_via_imagination.[seed].md +6 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<catalogize>.vs_diverge.[article].persp.save_compute.md +46 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>._.[article].frame.colloquial.i2.by_grok.md +64 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.[catalog].md +106 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.contrast.[demo].usecase.vs_userjourney.by_chatgpt.md +45 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.counter.[demo].usecase.flyer.by_chargpt.md +38 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.counter.[demo].walkability.phoenix.by_chargpt.md +41 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[demo].shear_force.scissors.by_grok.md +52 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[demo].tea.darjeeling.by_grok.md +50 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[demo].usecase.book_flight.by_grok.md +54 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[demo].usecase.order_food.by_chatgpt.md +40 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[demo].walkability.portland.by_chatgpt.i3.md +42 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[demo].walkability.portland.by_grok.i2.md +49 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[lesson].howto.md +28 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.structure.[article].i2.md +73 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.narrative.[demo].usecase.order_online.by_chatgpt.md +34 -0
- package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.walkthrough.[demo].usecase.book_online.by_chatgpt.md +47 -0
- package/dist/roles/thinker/briefs/librarian.tactics/[brief].verbiage.outline.over.narrative.md +55 -0
- package/dist/roles/thinker/briefs/logistics/term.logistics.[article].md +21 -0
- package/dist/roles/thinker/briefs/logistics/term.logistics.of_information.[article].md +22 -0
- package/dist/roles/thinker/briefs/logistics/term.logistics.of_knowledge.[article].md +29 -0
- package/dist/roles/thinker/briefs/physics/optics.focal.acuity.md +77 -0
- package/dist/roles/thinker/briefs/physics/optics.focal.breadth.md +74 -0
- package/dist/roles/thinker/briefs/physics/optics.focal.depth.md +77 -0
- package/dist/roles/thinker/briefs/physics/optics.focal.distance.md +92 -0
- package/dist/roles/thinker/briefs/physics/optics.focal.tradeoffs.md +107 -0
- package/dist/roles/thinker/briefs/style.words.lowercase.md +36 -0
- package/dist/roles/thinker/briefs/tactician/tactics.compose.traits_and_skills.[article].md +76 -0
- package/dist/roles/thinker/briefs/tactician/trait.articulation.[article].md +67 -0
- package/dist/roles/thinker/briefs/tactician/trait.purpose.[article].md +56 -0
- package/dist/roles/thinker/briefs/tactician/trait.vs_skill.[article].md +55 -0
- package/dist/roles/thinker/briefs/tactician/trait.vs_tactic.[article].md +70 -0
- package/dist/roles/thinker/briefs/terms.motive.intent.goal.md +46 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:42:52.441Z.9b5920a5f2286358.md +1 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:45:56.905Z.c41b7ee6c012dca7.md +1 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:46:26.625Z.550b8cabb776137d.md +1 -0
- 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 +13 -0
- 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 +13 -0
- 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 +13 -0
- 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 +12 -0
- 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 +12 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:39:04.900Z.f214cfb2b02fab75.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:40:21.875Z.f214cfb2b02fab75.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:45:04.181Z.f214cfb2b02fab75.md +3 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.2.md.goal/2025-08-18T05:06:49.995Z.528e7ccdbef5d0cb.md +3 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.3.md.goal/2025-08-18T05:07:30.951Z.528e7ccdbef5d0cb.md +3 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.4.md.goal/2025-08-18T05:08:11.225Z.528e7ccdbef5d0cb.md +3 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.5.md.goal/2025-08-18T05:09:02.754Z.508a8c044b22bfae.md +3 -0
- 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 +13 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.6.md.goal/2025-08-18T05:10:31.563Z.528e7ccdbef5d0cb.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.feedback/2025-08-18T04:50:08.771Z.6e29435be57e631a.md +1 -0
- 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 +13 -0
- 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 +13 -0
- 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 +13 -0
- 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 +13 -0
- 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 +12 -0
- 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 +12 -0
- 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 +12 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T04:46:51.080Z.528e7ccdbef5d0cb.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T04:47:37.295Z.528e7ccdbef5d0cb.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T05:06:06.946Z.528e7ccdbef5d0cb.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.md.goal/2025-08-18T05:11:59.369Z.516579c7a92b1b26.md +3 -0
- 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 +13 -0
- 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 +12 -0
- 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 +3 -0
- 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 +1 -0
- 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 +13 -0
- 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 +12 -0
- 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 +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.feedback/2025-08-18T04:59:17.249Z.b1420bd7f9bbf0df.md +1 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.feedback/2025-08-18T05:00:20.066Z.4841bbfbba6596ed.md +1 -0
- 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 +13 -0
- 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 +13 -0
- 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 +13 -0
- 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 +12 -0
- 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 +12 -0
- 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 +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.goal/2025-08-18T04:57:14.510Z.5d9b39222bdebaab.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.goal/2025-08-18T04:58:36.621Z.763f2b6f96e5eb78.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>.persp.implicit_question.[article].md.goal/2025-08-18T05:01:28.057Z.729168a4a51a9613.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:40:32.469Z.9a45a5da431061b7.md +69 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:43:00.496Z.e6c9d14fe7f196ad.md +86 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:45:09.820Z.496c31f5f6478ddb.md +69 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:46:02.394Z.ccbb435804f9a033.md +85 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical/2025-08-17T23:46:32.399Z.06fdb8bc5d327e89.md +85 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<cluster>._.[article].frame.tactical.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T04:47:52.480Z.a284db9ffbba3805.md +85 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T04:50:13.483Z.a284db9ffbba3805.md +85 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T05:06:18.798Z.2b58e354810a1e6d.md +85 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical/2025-08-18T05:12:09.225Z.f31c12b3cfed3c70.md +86 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2/2025-08-18T05:06:57.408Z.c68a7710adf0181d.md +71 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.2.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3/2025-08-18T05:07:43.297Z.82dd27d4f2ae7e71.md +81 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.3.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4/2025-08-18T05:08:20.573Z.19580b96c25a8226.md +77 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.4.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5/2025-08-18T05:09:06.597Z.523fa2836b3552d3.md +66 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.5.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6/2025-08-18T05:10:40.958Z.699e0e76881302b5.md +65 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.6.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>._.[article].frame.tactical.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1/2025-08-18T05:24:12.067Z.79b6025bbedf68c2.md +48 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.grades_from_context.[article].1.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T04:57:24.261Z.a3e52f604602d423.md +70 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T04:58:44.342Z.92ba73d496dee2fd.md +64 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T04:59:24.899Z.49858373ac837709.md +64 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T05:00:28.230Z.17eef006aff2c2e2.md +64 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article]/2025-08-18T05:01:38.340Z.9b64674c53f1407d.md +72 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2/2025-08-18T05:02:20.019Z.ec140a5feadeddb3.md +58 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2/2025-08-18T05:04:14.999Z.d3ae0f1e525de35b.md +65 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2.md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2.md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].2.md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.concept.md +13 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].md.foci.ponder.que.context.md +12 -0
- package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/<triage>.persp.implicit_question.[article].md.goal.md +3 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<cluster>._.[article].frame.tactical._.md +85 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<cluster>.vs_<diverge>.duality.[article].md +43 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<diverge>._.[article].frame.cognitive.[seed].md +4 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<diverge>._.[article].frame.tactical.md +89 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<elaborate>_vs_<elucidate>.[seed].md +1 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<enquestion>._.[article].md +113 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<enquestion>._.[gallery].plumber.diagnose.md +130 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<enquestion>._.[gallery].thinker.enquestion.md +125 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<enquestion>.tactic.perspectives.[article].md +36 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<triage>._.[article].frame.tactical.md +85 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<triage>.persp.grades_from_context.[article].md +48 -0
- package/dist/roles/thinker/briefs/thinker.tactics/<triage>.persp.implicit_question.[article].md +65 -0
- package/dist/roles/thinker/briefs/trait.chillnature.md +14 -0
- package/dist/roles/thinker/briefs/trait.ocd.md +5 -0
- package/dist/roles/thinker/briefs/worders/core.matmuls_vecmuls_elemuls.md +93 -0
- package/dist/roles/thinker/briefs/worders/core.transformers.as_origin.md +62 -0
- package/dist/roles/thinker/briefs/worders/core.transformers.self_attention.[article].md +93 -0
- package/dist/roles/thinker/briefs/worders/core.transformers.self_attention.[demo].ambig.bank.md +80 -0
- package/dist/roles/thinker/briefs/worders/core.transformers.self_attention.[demo].cat_sat.md +67 -0
- package/dist/roles/thinker/briefs/worders/force.repeat_input_structures.md +48 -0
- package/dist/roles/thinker/briefs/worders/knowledge.interdependence.[article].md +37 -0
- package/dist/roles/thinker/briefs/worders/knowledge.interdependence.[demo].domain.physics.md +30 -0
- package/dist/roles/thinker/briefs/worders/knowledge.internal_vs_external.[article].artist_vs_librarian.md +44 -0
- package/dist/roles/thinker/briefs/worders/knowledge.internal_vs_external.[demo].artist_vs_librarian.md +37 -0
- package/dist/roles/thinker/briefs/worders/knowledge.internal_vs_external.[demo].domain.physics.md +39 -0
- package/dist/roles/thinker/briefs/worders/knowledge.internalized.[article].md +35 -0
- package/dist/roles/thinker/briefs/worders/knowledge.internalized.[demo].artist.md +36 -0
- package/dist/roles/thinker/briefs/worders/knowledge.internalized.[demo].neural.md +37 -0
- package/dist/roles/thinker/briefs/worders/knowledge.internalized.[demo].pianist.md +34 -0
- package/dist/roles/thinker/briefs/worders/limits.rhyme.md +46 -0
- package/dist/roles/thinker/briefs/worders/limits.spell.md +49 -0
- package/dist/roles/thinker/briefs/worders/teach.via.library.examples.md +28 -0
- package/dist/roles/thinker/briefs/worders/teach.via.library.explanations_vs_examples.md +40 -0
- package/dist/roles/thinker/briefs/worders/trend.prefer_reuse.[seed].md +10 -0
- package/dist/roles/thinker/getThinkerBrief.Options.codegen.d.ts +10 -0
- package/dist/roles/thinker/getThinkerBrief.Options.codegen.js +204 -0
- package/dist/roles/thinker/getThinkerBrief.Options.codegen.js.map +1 -0
- package/dist/roles/thinker/getThinkerBrief.d.ts +13 -0
- package/dist/roles/thinker/getThinkerBrief.js +21 -0
- package/dist/roles/thinker/getThinkerBrief.js.map +1 -0
- package/dist/roles/thinker/getThinkerRole.d.ts +2 -0
- package/dist/roles/thinker/getThinkerRole.js +54 -0
- package/dist/roles/thinker/getThinkerRole.js.map +1 -0
- package/dist/roles/thinker/skills/brief.articulate/stepArticulate.d.ts +59 -0
- package/dist/roles/thinker/skills/brief.articulate/stepArticulate.js +97 -0
- package/dist/roles/thinker/skills/brief.articulate/stepArticulate.js.map +1 -0
- package/dist/roles/thinker/skills/brief.articulate/stepArticulate.skill.d.ts +30 -0
- package/dist/roles/thinker/skills/brief.articulate/stepArticulate.skill.js +125 -0
- package/dist/roles/thinker/skills/brief.articulate/stepArticulate.skill.js.map +1 -0
- package/dist/roles/thinker/skills/brief.articulate/stepArticulate.template.md +120 -0
- package/dist/roles/thinker/skills/brief.catalogize/stepCatalogize.d.ts +54 -0
- package/dist/roles/thinker/skills/brief.catalogize/stepCatalogize.js +74 -0
- package/dist/roles/thinker/skills/brief.catalogize/stepCatalogize.js.map +1 -0
- package/dist/roles/thinker/skills/brief.catalogize/stepCatalogize.skill.d.ts +28 -0
- package/dist/roles/thinker/skills/brief.catalogize/stepCatalogize.skill.js +124 -0
- package/dist/roles/thinker/skills/brief.catalogize/stepCatalogize.skill.js.map +1 -0
- package/dist/roles/thinker/skills/brief.demonstrate/stepDemonstrate.d.ts +59 -0
- package/dist/roles/thinker/skills/brief.demonstrate/stepDemonstrate.js +103 -0
- package/dist/roles/thinker/skills/brief.demonstrate/stepDemonstrate.js.map +1 -0
- package/dist/roles/thinker/skills/brief.demonstrate/stepDemonstrate.skill.d.ts +30 -0
- package/dist/roles/thinker/skills/brief.demonstrate/stepDemonstrate.skill.js +138 -0
- package/dist/roles/thinker/skills/brief.demonstrate/stepDemonstrate.skill.js.map +1 -0
- package/dist/roles/thinker/skills/brief.demonstrate/stepDemonstrate.template.md +135 -0
- package/dist/roles/thinker/skills/khue.cluster/stepCluster.d.ts +57 -0
- package/dist/roles/thinker/skills/khue.cluster/stepCluster.js +91 -0
- package/dist/roles/thinker/skills/khue.cluster/stepCluster.js.map +1 -0
- package/dist/roles/thinker/skills/khue.cluster/stepCluster.skill.d.ts +29 -0
- package/dist/roles/thinker/skills/khue.cluster/stepCluster.skill.js +127 -0
- package/dist/roles/thinker/skills/khue.cluster/stepCluster.skill.js.map +1 -0
- package/dist/roles/thinker/skills/khue.cluster/stepCluster.template.md +134 -0
- package/dist/roles/thinker/skills/khue.diverge/stepDiverge.d.ts +57 -0
- package/dist/roles/thinker/skills/khue.diverge/stepDiverge.js +92 -0
- package/dist/roles/thinker/skills/khue.diverge/stepDiverge.js.map +1 -0
- package/dist/roles/thinker/skills/khue.diverge/stepDiverge.skill.d.ts +29 -0
- package/dist/roles/thinker/skills/khue.diverge/stepDiverge.skill.js +112 -0
- package/dist/roles/thinker/skills/khue.diverge/stepDiverge.skill.js.map +1 -0
- package/dist/roles/thinker/skills/khue.diverge/stepDiverge.template.md +110 -0
- package/dist/roles/thinker/skills/khue.instantiate/stepInstantiate.d.ts +55 -0
- package/dist/roles/thinker/skills/khue.instantiate/stepInstantiate.js +75 -0
- package/dist/roles/thinker/skills/khue.instantiate/stepInstantiate.js.map +1 -0
- package/dist/roles/thinker/skills/khue.instantiate/stepInstantiate.skill.d.ts +28 -0
- package/dist/roles/thinker/skills/khue.instantiate/stepInstantiate.skill.js +136 -0
- package/dist/roles/thinker/skills/khue.instantiate/stepInstantiate.skill.js.map +1 -0
- package/dist/roles/thinker/skills/khue.instantiate/stepInstantiate.template.md +73 -0
- package/dist/roles/thinker/skills/khue.triage/stepTriage.d.ts +57 -0
- package/dist/roles/thinker/skills/khue.triage/stepTriage.js +93 -0
- package/dist/roles/thinker/skills/khue.triage/stepTriage.js.map +1 -0
- package/dist/roles/thinker/skills/khue.triage/stepTriage.skill.d.ts +29 -0
- package/dist/roles/thinker/skills/khue.triage/stepTriage.skill.js +127 -0
- package/dist/roles/thinker/skills/khue.triage/stepTriage.skill.js.map +1 -0
- package/dist/roles/thinker/skills/khue.triage/stepTriage.template.md +128 -0
- package/license.md +21 -0
- package/package.json +104 -0
- package/readme.md +91 -0
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# .brief.demo: `walkability` via `counter` = `phoenix suburbs`
|
|
2
|
+
|
|
3
|
+
## π‘ concept
|
|
4
|
+
walkability is the measure of how friendly an area is to walking, determined by the proximity of daily needs, the quality of pedestrian infrastructure, and the safety and comfort of the walking environment.
|
|
5
|
+
|
|
6
|
+
## β question
|
|
7
|
+
> what is a counter-example of walkability?
|
|
8
|
+
|
|
9
|
+
## π counter-example: phoenix suburbs
|
|
10
|
+
|
|
11
|
+
### π.π what
|
|
12
|
+
|
|
13
|
+
> what are the phoenix suburbs?
|
|
14
|
+
|
|
15
|
+
the sprawling suburbs around phoenix, arizona, are characterized by low-density housing, wide arterial roads, and zoning that separates residential areas from commercial and institutional uses. daily needs are typically spread out across miles, accessible primarily by car.
|
|
16
|
+
|
|
17
|
+
- **long distances to daily needs**
|
|
18
|
+
- grocery stores, schools, and cafes located far from most homes
|
|
19
|
+
- *example:* a typical subdivision may require a 15β20 minute drive to reach basic shopping
|
|
20
|
+
- **disconnected infrastructure**
|
|
21
|
+
- large blocks, wide intersections, and missing sidewalks
|
|
22
|
+
- *example:* six-lane arterial roads without pedestrian crossings for half a mile
|
|
23
|
+
- **unsafe crossings**
|
|
24
|
+
- intersections designed for vehicle throughput, not pedestrians
|
|
25
|
+
- *example:* high-speed right-turn lanes with no pedestrian refuge
|
|
26
|
+
- **weak transit integration**
|
|
27
|
+
- bus routes are sparse and stops often lack safe walking access
|
|
28
|
+
- *example:* bus stops located on roads without sidewalks or shelters
|
|
29
|
+
|
|
30
|
+
### π.π how
|
|
31
|
+
|
|
32
|
+
> how is the phoenix suburban pattern a counter-example of walkability?
|
|
33
|
+
|
|
34
|
+
phoenix suburbs highlight the absence of walkability through **distance**, **design**, and **dependence**:
|
|
35
|
+
|
|
36
|
+
- **distance**: residential and commercial areas are so spread out that walking is impractical for daily errands.
|
|
37
|
+
- **design**: streets prioritize car speed and capacity, making walking unpleasant and often dangerous.
|
|
38
|
+
- **dependence**: car ownership becomes a necessity, as walking and transit provide no viable alternative.
|
|
39
|
+
- **comfort and safety**: the harsh desert climate, combined with limited shade and long stretches without sidewalks, further discourages walking.
|
|
40
|
+
|
|
41
|
+
this counter-example shows that when urban planning prioritizes cars over people, walkability disappearsβunderscoring why compact, mixed-use, and pedestrian-first design is essential for creating walkable places.
|
|
@@ -0,0 +1,52 @@
|
|
|
1
|
+
# π§© .brief.demo: `mechanical shear force` via `example` = `scissors`
|
|
2
|
+
|
|
3
|
+
## π‘ Concept
|
|
4
|
+
|
|
5
|
+
Mechanical shear force is a type of force that acts parallel to a materialβs surface, causing one portion to slide past another, often leading to cutting, deformation, or fracture of the material.
|
|
6
|
+
|
|
7
|
+
## β Question
|
|
8
|
+
|
|
9
|
+
> What is an example of mechanical shear force?
|
|
10
|
+
|
|
11
|
+
## π Example: Scissors Cutting Paper
|
|
12
|
+
|
|
13
|
+
### π.π What
|
|
14
|
+
|
|
15
|
+
> What is scissors cutting paper?
|
|
16
|
+
|
|
17
|
+
Scissors cutting paper is a common action where two sharp blades slide past each other to slice through a sheet of paper, applying a mechanical force that separates the material. This everyday process, used in households and offices, relies on the precise interaction of blades to achieve a clean cut.
|
|
18
|
+
|
|
19
|
+
- **Historical Context**
|
|
20
|
+
- **Invention of Scissors**: Originated around 1500 BCE in ancient Egypt, with modern pivoted scissors refined in the 18th century for precision tasks.
|
|
21
|
+
- **Evolution of Design**: Advanced from simple metal blades to ergonomic handles and specialized types, like crafting or industrial scissors.
|
|
22
|
+
- **Physical Components**
|
|
23
|
+
- **Blade Structure**: Consists of two sharp, metal blades pivoted at a central point, allowing them to slide against each other.
|
|
24
|
+
- **Handle Mechanism**: Ergonomic handles enable the user to apply force, controlling the bladesβ movement and pressure.
|
|
25
|
+
- **Material Interaction**: The blades contact the paper at a small, localized area, focusing the applied force for effective cutting.
|
|
26
|
+
- **Common Applications**
|
|
27
|
+
- **Household Use**: Employed for tasks like cutting paper for crafts, wrapping, or office work, accessible to all ages.
|
|
28
|
+
- **Industrial Variants**: Used in larger forms, like shears, for cutting tougher materials in manufacturing or textiles.
|
|
29
|
+
- **Educational Role**: Taught in schools for art projects, demonstrating basic mechanical principles in action.
|
|
30
|
+
|
|
31
|
+
### π.π How
|
|
32
|
+
|
|
33
|
+
> How is it an example of mechanical shear force?
|
|
34
|
+
|
|
35
|
+
Scissors cutting paper exemplifies mechanical shear force by applying parallel forces through sliding blades to sever the paper, demonstrating the conceptβs role in material deformation and separation. The process highlights shear forceβs characteristics of localized stress, sliding motion, and structural impact in a practical, observable way.
|
|
36
|
+
|
|
37
|
+
- **Application of Parallel Forces**
|
|
38
|
+
- **Blade Sliding**: The blades move parallel to each other, exerting opposing forces on the paperβs surface, creating shear stress.
|
|
39
|
+
- **Localized Contact**: The force concentrates at the point where the blades meet, maximizing shear effect on a small area.
|
|
40
|
+
- **Force Transmission**: User pressure on the handles transfers directly to the blades, amplifying the shear force applied.
|
|
41
|
+
- **Material Deformation**
|
|
42
|
+
- **Paper Shearing**: The paperβs fibers are pushed apart as the blades slide, causing the material to split cleanly.
|
|
43
|
+
- **No Compression**: Unlike crushing, the bladesβ action avoids compressing the paper, focusing solely on shear-induced separation.
|
|
44
|
+
- **Clean Cut**: The result is a smooth edge, showing shear forceβs ability to precisely fracture materials.
|
|
45
|
+
- **Mechanical Advantage**
|
|
46
|
+
- **Lever Action**: The pivot acts as a fulcrum, multiplying the userβs hand force into greater shear force at the blades.
|
|
47
|
+
- **Blade Angle**: The sharp, angled edges reduce the contact area, increasing shear stress for efficient cutting.
|
|
48
|
+
- **Design Efficiency**: Ergonomic scissors optimize force transfer, making shear force application intuitive and effective.
|
|
49
|
+
- **Observable Outcomes**
|
|
50
|
+
- **Visible Separation**: The paper splits visibly as the blades close, directly illustrating shear forceβs cutting effect.
|
|
51
|
+
- **Material Response**: Thin materials like paper yield easily, while thicker ones resist, showing shear forceβs dependence on material strength.
|
|
52
|
+
- **Practical Impact**: The clean cut enables precise tasks, connecting shear force to everyday utility and engineering principles.
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
# π§© .brief.demo: `tea` via `example` = `darjeeling`
|
|
2
|
+
|
|
3
|
+
## π‘ Concept
|
|
4
|
+
|
|
5
|
+
Tea is a beverage made by steeping processed leaves, buds, or twigs of the Camellia sinensis plant in hot water, valued for its diverse flavors, cultural significance, and health benefits.
|
|
6
|
+
|
|
7
|
+
## β Question
|
|
8
|
+
|
|
9
|
+
> What is an example of tea?
|
|
10
|
+
|
|
11
|
+
## π Example: Darjeeling Tea
|
|
12
|
+
|
|
13
|
+
### π.π What
|
|
14
|
+
|
|
15
|
+
> What is Darjeeling tea?
|
|
16
|
+
|
|
17
|
+
Darjeeling tea is a premium black tea grown in the Darjeeling region of West Bengal, India, renowned for its delicate, muscatel flavor and floral aroma. Often called the βChampagne of teas,β itβs cultivated in high-altitude estates and celebrated for its unique terroir-driven qualities.
|
|
18
|
+
|
|
19
|
+
- **Historical Context**
|
|
20
|
+
- **Origins in India**: Introduced in the 19th century by British colonial planters, inspired by Chinese tea cultivation techniques.
|
|
21
|
+
- **Global Recognition**: Gained international fame for its distinct taste, earning a Geographical Indication (GI) status to protect its authenticity.
|
|
22
|
+
- **Production Characteristics**
|
|
23
|
+
- **High-Altitude Cultivation**: Grown at elevations of 2,000β7,000 feet in the Himalayan foothills, contributing to its unique flavor profile.
|
|
24
|
+
- **Seasonal Flushes**: Harvested in distinct seasons (first flush in spring, second flush in summer), each offering different taste notes, from light and floral to robust and fruity.
|
|
25
|
+
- **Cultural Significance**
|
|
26
|
+
- **Local Tradition**: A cornerstone of Darjeelingβs economy and culture, with tea estates employing thousands and shaping regional identity.
|
|
27
|
+
- **Global Appeal**: Prized by tea connoisseurs worldwide, often served in high-end tea houses and ceremonies.
|
|
28
|
+
|
|
29
|
+
### π.π How
|
|
30
|
+
|
|
31
|
+
> How is it an example of tea?
|
|
32
|
+
|
|
33
|
+
Darjeeling tea exemplifies the concept of tea through its meticulous cultivation and processing from Camellia sinensis, its diverse flavor profiles, and its deep cultural and health-related significance. Its global reputation and versatility in preparation highlight the essence of tea as a beverage and cultural staple.
|
|
34
|
+
|
|
35
|
+
- **Camellia Sinensis Base**
|
|
36
|
+
- **Plant Source**: Made from the leaves of the Camellia sinensis plant, aligning with the core definition of true tea.
|
|
37
|
+
- **Processing Techniques**: Undergoes withering, rolling, oxidation, and drying, typical of black tea production, to develop its signature flavor.
|
|
38
|
+
- **Varietal Specificity**: Uses the Chinese varietal of Camellia sinensis, adapted to Darjeelingβs unique climate and soil.
|
|
39
|
+
- **Flavor and Aroma Diversity**
|
|
40
|
+
- **Muscatel Notes**: Known for a distinctive grape-like flavor, especially in second flush teas, showcasing teaβs range of taste profiles.
|
|
41
|
+
- **Floral Undertones**: First flush teas offer light, floral aromas, appealing to those seeking delicate tea experiences.
|
|
42
|
+
- **Seasonal Variation**: Different harvests (flushes) provide varied flavors, illustrating teaβs versatility within a single origin.
|
|
43
|
+
- **Cultural Role**
|
|
44
|
+
- **Social Rituals**: Consumed in afternoon tea settings globally, from British high tea to casual sipping in India, reflecting teaβs social importance.
|
|
45
|
+
- **Economic Impact**: Supports Darjeelingβs tea estates, employing local communities and reinforcing teaβs role in cultural heritage.
|
|
46
|
+
- **Ceremonial Use**: Featured in tea tastings and pairings, highlighting teaβs place in refined cultural practices.
|
|
47
|
+
- **Health and Wellness Benefits**
|
|
48
|
+
- **Antioxidant Properties**: Contains polyphenols, linked to reducing oxidative stress and supporting heart health.
|
|
49
|
+
- **Caffeine Content**: Provides a mild stimulant effect, offering an energy boost without coffeeβs intensity.
|
|
50
|
+
- **Mental Clarity**: L-theanine promotes relaxation and focus, exemplifying teaβs calming yet invigorating qualities.
|
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
# π§© .brief.demo: `use case` via `example` = `booking flight`
|
|
2
|
+
|
|
3
|
+
## π‘ Concept
|
|
4
|
+
|
|
5
|
+
A use case describes how a user interacts with a system to achieve a specific goal, detailing actors, steps, and system responses to define functional requirements in software development.
|
|
6
|
+
|
|
7
|
+
## β Question
|
|
8
|
+
|
|
9
|
+
> What is an example of a use case?
|
|
10
|
+
|
|
11
|
+
## π Example: Booking a Flight on a Travel Website
|
|
12
|
+
|
|
13
|
+
### π.π What
|
|
14
|
+
|
|
15
|
+
> What is the use case "booking a flight on a travel website"?
|
|
16
|
+
|
|
17
|
+
The use case "booking a flight on a travel website" is a structured description of how a traveler uses an online platform like Expedia or Kayak to purchase an airline ticket.
|
|
18
|
+
|
|
19
|
+
- **Actor**: Traveler (the user seeking to book a flight).
|
|
20
|
+
- **Goal**: To purchase an airline ticket for a chosen destination and date.
|
|
21
|
+
- **Preconditions**: The user has access to the travel website via a web browser or mobile app and a valid payment method.
|
|
22
|
+
- **Main Flow**:
|
|
23
|
+
1. **User**: Navigates to the websiteβs homepage and enters departure city, destination, travel dates, and passenger details, then clicks βSearch.β
|
|
24
|
+
2. **System**: Displays a list of available flights with details (airlines, times, prices).
|
|
25
|
+
3. **User**: Selects a preferred flight and optional extras (e.g., seat selection, baggage).
|
|
26
|
+
4. **System**: Prompts for passenger details (name, contact info) and payment information.
|
|
27
|
+
5. **User**: Enters payment details and confirms the booking.
|
|
28
|
+
6. **System**: Processes payment, books the ticket, and sends a confirmation email with the ticket.
|
|
29
|
+
- **Exceptions**:
|
|
30
|
+
- **No Flights Available**: If no flights match the criteria, the system displays an error and suggests alternative dates or destinations.
|
|
31
|
+
- **Payment Failure**: If payment fails, the system notifies the user and prompts re-entry or an alternative payment method.
|
|
32
|
+
|
|
33
|
+
### π.π How
|
|
34
|
+
|
|
35
|
+
> How is it an example of a use case?
|
|
36
|
+
|
|
37
|
+
The use case "booking a flight on a travel website" exemplifies a use case by providing a structured description of a travelerβs interaction with a system to achieve a specific goal, capturing user actions, system responses, and edge cases. It serves as a clear blueprint for developers, illustrating how use cases define functional requirements and ensure user-centric system design.
|
|
38
|
+
|
|
39
|
+
- **Defined Actor and Goal**
|
|
40
|
+
- **Traveler as Actor**: Specifies the user (traveler) as the primary actor, aligning with the use caseβs focus on who interacts with the system.
|
|
41
|
+
- **Clear Objective**: The goal of purchasing a ticket drives the interaction, a core element of any use case.
|
|
42
|
+
- **System Role**: The travel website facilitates the goal, acting as the system under consideration.
|
|
43
|
+
- **Structured Interaction Flow**
|
|
44
|
+
- **Sequential Steps**: Details a clear sequence (search, select, pay), mirroring the step-by-step flow typical of use case descriptions.
|
|
45
|
+
- **User-System Dialogue**: Alternates between user actions (e.g., entering details) and system responses (e.g., displaying flights), reflecting use case dynamics.
|
|
46
|
+
- **Preconditions Included**: Specifies requirements like internet access and payment method, setting the stage for the interaction.
|
|
47
|
+
- **Exception Handling**
|
|
48
|
+
- **Error Scenarios**: Addresses cases like no flights or payment failure, showing how use cases account for alternate paths.
|
|
49
|
+
- **User Guidance**: System responses (e.g., error messages, prompts) ensure users can navigate issues, a key use case feature.
|
|
50
|
+
- **Robustness**: Captures edge cases, ensuring the system is designed to handle real-world challenges.
|
|
51
|
+
- **Requirements Specification**
|
|
52
|
+
- **Functional Needs**: Outlines needs like search functionality and payment processing, guiding developers on system features.
|
|
53
|
+
- **Security Focus**: Highlights secure payment handling, a critical requirement derived from the use case.
|
|
54
|
+
- **Stakeholder Clarity**: Provides a clear reference for developers, testers, and designers to align on user needs and system behavior.
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
# .brief.demo: `use case` via `example` = `online food delivery`
|
|
2
|
+
|
|
3
|
+
## π‘ concept
|
|
4
|
+
a use case describes how a user interacts with a system to achieve a specific goal, detailing the steps, actors, and system responses involved in the interaction.
|
|
5
|
+
|
|
6
|
+
## β question
|
|
7
|
+
> what is an example of a use case?
|
|
8
|
+
|
|
9
|
+
## π example: online food delivery
|
|
10
|
+
|
|
11
|
+
### π.π what
|
|
12
|
+
|
|
13
|
+
> what is the online food delivery use case?
|
|
14
|
+
|
|
15
|
+
the online food delivery use case outlines how a customer orders food through a delivery platform (like doordash or uber eats), and how the system responds at each stage to fulfill the request. it represents a common digital interaction where multiple actors (customer, restaurant, courier, system) collaborate to achieve the userβs goal: receiving a meal at home.
|
|
16
|
+
|
|
17
|
+
- **actors involved**
|
|
18
|
+
- customer places an order
|
|
19
|
+
- restaurant receives and prepares food
|
|
20
|
+
- courier picks up and delivers the order
|
|
21
|
+
- system coordinates communication and payments
|
|
22
|
+
- **goal**
|
|
23
|
+
- customer receives desired food at their location in a timely manner
|
|
24
|
+
- **context**
|
|
25
|
+
- mobile app or website interface, integrated with payment and logistics
|
|
26
|
+
|
|
27
|
+
### π.π how
|
|
28
|
+
|
|
29
|
+
> how is online food delivery an example of a use case?
|
|
30
|
+
|
|
31
|
+
it demonstrates a use case by showing the **sequence of interactions**:
|
|
32
|
+
|
|
33
|
+
1. **customer action**: browses menu, selects food, and confirms order.
|
|
34
|
+
2. **system response**: sends order details to the restaurant, processes payment, provides confirmation to customer.
|
|
35
|
+
3. **restaurant action**: prepares the food and marks it ready.
|
|
36
|
+
4. **system response**: dispatches courier notification and tracks delivery.
|
|
37
|
+
5. **courier action**: picks up order and delivers to customerβs address.
|
|
38
|
+
6. **system response**: updates tracking, confirms delivery, and collects feedback.
|
|
39
|
+
|
|
40
|
+
this example embodies the concept of a use case by mapping out actors, steps, and goals in a structured way, showing how user intent translates into system-supported outcomes.
|
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
# .brief.demo: `walkability` via `example` = `downtown portland`
|
|
2
|
+
|
|
3
|
+
## π‘ concept
|
|
4
|
+
walkability is the measure of how friendly an area is to walking, determined by the proximity of daily needs, the quality of pedestrian infrastructure, and the safety and comfort of the walking environment.
|
|
5
|
+
|
|
6
|
+
## β question
|
|
7
|
+
> what is an example of walkability?
|
|
8
|
+
|
|
9
|
+
## π example: downtown portland
|
|
10
|
+
|
|
11
|
+
### π.π what
|
|
12
|
+
|
|
13
|
+
> what is downtown portland?
|
|
14
|
+
|
|
15
|
+
downtown portland is a central neighborhood in portland, oregon, known for its compact urban grid, accessible public transit, and pedestrian-friendly design. the area integrates commercial, residential, and cultural spaces within short walking distances.
|
|
16
|
+
|
|
17
|
+
- **daily needs within reach**
|
|
18
|
+
- groceries, cafes, and schools located within 5β10 minutes by foot
|
|
19
|
+
- *example:* whole foods and local corner markets
|
|
20
|
+
- *example:* elementary schools and daycare facilities
|
|
21
|
+
- **continuous walking network**
|
|
22
|
+
- sidewalks, curb ramps, and bike lanes that form a safe, connected grid
|
|
23
|
+
- *example:* protected bike lanes on broadway
|
|
24
|
+
- **pedestrian-priority crossings**
|
|
25
|
+
- crosswalks, countdown signals, and curb extensions
|
|
26
|
+
- *example:* marked intersections with pedestrian-first light cycles
|
|
27
|
+
- **transit integration**
|
|
28
|
+
- max light rail, bus, and streetcar stops accessible directly from sidewalks
|
|
29
|
+
- *example:* pioneer courthouse square transit hub
|
|
30
|
+
|
|
31
|
+
### π.π how
|
|
32
|
+
|
|
33
|
+
> how is downtown portland an example of walkability?
|
|
34
|
+
|
|
35
|
+
downtown portland exemplifies walkability because it combines **proximity**, **infrastructure**, and **integration**:
|
|
36
|
+
|
|
37
|
+
- **proximity**: mixed-use zoning keeps housing, workplaces, shops, and cultural venues close together, reducing reliance on cars.
|
|
38
|
+
- **infrastructure**: the city grid ensures short blocks, frequent intersections, and pedestrian-scale street design that prioritize people on foot.
|
|
39
|
+
- **integration**: public transit connects seamlessly with sidewalks, allowing trips to extend beyond walking range without breaking the pedestrian experience.
|
|
40
|
+
- **safety and comfort**: traffic calming, green streets, and shaded sidewalks create a walking environment that is both secure and inviting.
|
|
41
|
+
|
|
42
|
+
together, these factors transform downtown portland into a living demonstration of how urban design can encourage walking as the default mode of daily life.
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# π§© .brief.demo: `walkability` via `example` = `portland`
|
|
2
|
+
|
|
3
|
+
## π‘ Concept
|
|
4
|
+
|
|
5
|
+
Walkability refers to how friendly an area is to walking, characterized by safe, accessible, and pleasant environments that encourage pedestrian activity, reduce car dependency, and promote community interaction.
|
|
6
|
+
|
|
7
|
+
## β Question
|
|
8
|
+
*What is an example of walkability?*
|
|
9
|
+
|
|
10
|
+
## π Example: Portlandβs Pearl District
|
|
11
|
+
|
|
12
|
+
### π.π What
|
|
13
|
+
|
|
14
|
+
What is Portlandβs Pearl District?
|
|
15
|
+
|
|
16
|
+
The Pearl District is a vibrant, urban neighborhood in Portland, Oregon, known for its transformation from an industrial area into a cultural hub with art galleries, lofts, and lively public spaces. Once home to warehouses and rail yards, itβs now a model of modern urban living with a focus on community and accessibility.
|
|
17
|
+
|
|
18
|
+
- **Historical Context**
|
|
19
|
+
- **Industrial Origins**: Began as a late 19th-century warehouse and rail yard district, redeveloped in the 1990s into a residential and commercial area.
|
|
20
|
+
- **Urban Renewal**: Old industrial buildings were converted into lofts, galleries, and shops, revitalizing the area into a bustling neighborhood.
|
|
21
|
+
- **Neighborhood Character**
|
|
22
|
+
- **Cultural Hub**: Features prominent art galleries, boutique shops, and restaurants, drawing artists, residents, and tourists.
|
|
23
|
+
- **Modern Design**: Combines historic brick buildings with sleek, contemporary architecture in a compact grid layout.
|
|
24
|
+
- **Community Features**
|
|
25
|
+
- **Public Parks**: Includes Jamison Square and Tanner Springs Park, offering green spaces for recreation and community events.
|
|
26
|
+
- **Diverse Housing**: Provides high-rise condos, converted lofts, and some affordable housing, fostering a varied resident base.
|
|
27
|
+
|
|
28
|
+
### π.π How
|
|
29
|
+
|
|
30
|
+
How is it an example of walkability?
|
|
31
|
+
|
|
32
|
+
The Pearl District exemplifies walkability through its compact, mixed-use design, robust pedestrian infrastructure, and vibrant community spaces that make walking safe, convenient, and enjoyable. Its integration with transit and focus on sustainability further enhance its pedestrian-friendly environment.
|
|
33
|
+
|
|
34
|
+
- **Mixed-Use Accessibility**
|
|
35
|
+
- **Proximity of Amenities**: Shops, cafes, galleries, and offices are within a 10β15 minute walk, enabling car-free daily routines.
|
|
36
|
+
- **Street-Level Engagement**: Ground-floor businesses with outdoor seating create lively, walkable destinations.
|
|
37
|
+
- **Compact Layout**: Short blocks and a grid pattern minimize walking distances, encouraging pedestrian travel.
|
|
38
|
+
- **Pedestrian-Friendly Infrastructure**
|
|
39
|
+
- **Safe Sidewalks**: Wide, ADA-compliant sidewalks and frequent crosswalks with countdown timers ensure accessibility and safety.
|
|
40
|
+
- **Traffic Calming**: Speed bumps and narrowed streets reduce vehicle speeds, prioritizing pedestrian movement.
|
|
41
|
+
- **Aesthetic Appeal**: Tree-lined streets and public art enhance the walking experience, making it pleasant and inviting.
|
|
42
|
+
- **Transit Integration**
|
|
43
|
+
- **Streetcar Access**: The Portland Streetcar connects the district to downtown and other areas, supporting car-free mobility.
|
|
44
|
+
- **Light Rail Proximity**: Nearby MAX light rail stations provide regional access, complementing walking routes.
|
|
45
|
+
- **Bike Synergy**: Dedicated bike lanes and racks integrate cycling with walking, enhancing multimodal options.
|
|
46
|
+
- **Community and Environmental Benefits**
|
|
47
|
+
- **Social Connectivity**: Plazas and events like farmersβ markets foster interactions, making walking a community-building activity.
|
|
48
|
+
- **Sustainability**: Reduced car use lowers emissions, aligning with Portlandβs eco-friendly ethos.
|
|
49
|
+
- **Health Promotion**: Walkable access to amenities encourages physical activity, supporting resident well-being.
|
package/dist/roles/thinker/briefs/librarian.tactics/<demonstrate>.variants.example.[lesson].howto.md
ADDED
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
# π§© .brief.lesson: howto create a .brief.demo via example
|
|
2
|
+
|
|
3
|
+
## π― Objective
|
|
4
|
+
|
|
5
|
+
Learn how to create a `.brief.demo`, a concise document that demonstrates a concept through a specific example, with a focus on instantiating the concept in a dedicated βWhatβ section to make it clear and tangible.
|
|
6
|
+
|
|
7
|
+
## π Steps
|
|
8
|
+
|
|
9
|
+
1. **Define the Concept Clearly**
|
|
10
|
+
- Write a brief, one-sentence definition of the concept to set the context for the demonstration.
|
|
11
|
+
- **Example**: For the concept of a use case, define it as βA use case describes how a user interacts with a system to achieve a goal, detailing actors, steps, and system responses.β
|
|
12
|
+
2. **Choose a Representative Example**
|
|
13
|
+
- Select a single, concrete example that directly embodies the concept and is relatable to the audience.
|
|
14
|
+
- **Example**: For shear force, choose βscissors cutting paperβ to show parallel forces causing material deformation, a clear and familiar instance.
|
|
15
|
+
3. **Instantiate the Concept in the βWhatβ Section**
|
|
16
|
+
- Present the example as a direct instance of the concept, using a structure that mirrors its natural form (e.g., a use case template for βBooking a Flight,β a scenario for shear force).
|
|
17
|
+
- Avoid general descriptions; focus on showing the concept in action.
|
|
18
|
+
- **Example**: For a use case, present a structured description with Actor (Traveler), Goal (purchase a ticket), Main Flow (search, select, pay), and Exceptions (no flights, payment failure).
|
|
19
|
+
4. **Explain the Connection in a βHowβ Section**
|
|
20
|
+
- Detail how the example embodies the conceptβs key characteristics, using a structured format like a bulleted list to ensure clarity and depth.
|
|
21
|
+
- **Example**: For βBooking a Flight,β explain how its structured flow and exception handling align with a use caseβs role in defining system requirements.
|
|
22
|
+
|
|
23
|
+
## π Key Considerations
|
|
24
|
+
|
|
25
|
+
- **Instantiation is Key**: The βWhatβ section should always present the example as an instance of the concept (e.g., a use case template, not just a booking process) to directly demonstrate its essence, making the concept tangible.
|
|
26
|
+
- **Keep It Concise**: Avoid verbose outlines or excessive sub-bullets; focus on the exampleβs core elements to maintain clarity, as seen in the streamlined βBooking a Flightβ use case.
|
|
27
|
+
- **Adapt to Concept Type**: Tailor the instantiation to the conceptβs natureβuse templates for meta-concepts (e.g., use case), scenarios for physical concepts (e.g., shear force), or specific items for tangible concepts (e.g., Darjeeling tea).
|
|
28
|
+
- **Ensure Relatability**: Choose examples that resonate with the audience (e.g., scissors for shear force, a familiar website for booking), ensuring accessibility across technical or abstract concepts.
|
|
@@ -0,0 +1,73 @@
|
|
|
1
|
+
# π§© .brief.article: `recommended structure of .brief.demo via example`
|
|
2
|
+
|
|
3
|
+
## π introduction
|
|
4
|
+
|
|
5
|
+
a `.brief.demo` is a streamlined, example-driven document designed to illustrate a concept by presenting a specific instance of it in a structured markdown format. by recommending a standardized structure with a focus on instantiating the concept, it ensures clarity, engagement, and adaptability for diverse audiences, from students to professionals.
|
|
6
|
+
|
|
7
|
+
## π the core components
|
|
8
|
+
|
|
9
|
+
the `.brief.demo` follows a logical progression to build understanding step by step.
|
|
10
|
+
|
|
11
|
+
### 1. concept definition (π‘)
|
|
12
|
+
a concise, one-sentence definition of the concept, setting the foundation without overwhelming the reader. it acts as the entry point, ensuring everyone starts on the same page.
|
|
13
|
+
|
|
14
|
+
- **purpose**: define the concept succinctly, avoiding jargon where possible.
|
|
15
|
+
|
|
16
|
+
### 2. guiding question (β)
|
|
17
|
+
a block-quoted question focuses the demo on a specific inquiry, typically:
|
|
18
|
+
`> what is an example of [concept]?`
|
|
19
|
+
|
|
20
|
+
- **purpose**: to create curiosity and direct attention to the exampleβs role in answering the query.
|
|
21
|
+
|
|
22
|
+
### 3. example presentation (π)
|
|
23
|
+
this is the heart of the `.brief.demo`, introducing the chosen example and breaking it into two subsections: **what** and **how**.
|
|
24
|
+
|
|
25
|
+
#### π.π what
|
|
26
|
+
instantiates the concept by presenting the example in its most representative form. the structure used here is imagined to best fit the concept being demonstrated.
|
|
27
|
+
|
|
28
|
+
**purpose**: to make the concept tangible rather than abstract.
|
|
29
|
+
|
|
30
|
+
#### π.π how
|
|
31
|
+
explains how the instantiated example embodies the concept. the structure of this explanation is also imagined to best fit the concept.
|
|
32
|
+
|
|
33
|
+
**purpose**: to provide depth and analysis, linking the instance back to the definition in a systematic way.
|
|
34
|
+
|
|
35
|
+
### 4. placeholder example of `.brief.demo` structure
|
|
36
|
+
|
|
37
|
+
\`\`\`markdown
|
|
38
|
+
# π§© .brief.demo: `[concept]` via `example` = `[example]`
|
|
39
|
+
|
|
40
|
+
## π‘ concept
|
|
41
|
+
[brief definition of the concept]
|
|
42
|
+
|
|
43
|
+
## β question
|
|
44
|
+
> what is an example of [concept]?
|
|
45
|
+
|
|
46
|
+
## π example: [example title]
|
|
47
|
+
|
|
48
|
+
### π.π what
|
|
49
|
+
|
|
50
|
+
> What is [specific example of the concept]?
|
|
51
|
+
|
|
52
|
+
[brief introduction to the example]
|
|
53
|
+
|
|
54
|
+
[structured instantiation imagined to fit the concept]
|
|
55
|
+
|
|
56
|
+
### π.π how
|
|
57
|
+
|
|
58
|
+
> How is it an example of [concept]?
|
|
59
|
+
|
|
60
|
+
[brief explanation of how it embodies the concept]
|
|
61
|
+
|
|
62
|
+
[structured explanation imagined to fit the concept]
|
|
63
|
+
\`\`\`
|
|
64
|
+
|
|
65
|
+
## β
benefits and adaptability
|
|
66
|
+
|
|
67
|
+
the `.brief.demo` structure excels in its adaptability:
|
|
68
|
+
|
|
69
|
+
- **clarity through instantiation**: the βwhatβ section transforms abstractions into concrete, example-driven forms.
|
|
70
|
+
- **depth without overload**: the βhowβ section provides analysis through whatever framing best matches the concept, ensuring precision without unnecessary bulk.
|
|
71
|
+
- **versatility across domains**: whether scientific, technical, social, or abstract, the structure adapts by letting the instance shape its own presentation.
|
|
72
|
+
|
|
73
|
+
this makes `.brief.demo` a powerful tool for education, documentation, and knowledge sharing, consistently delivering clear and engaging concept demonstrations.
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
# .brief.demo: `use case` via `narrative` = `ordering dinner on an app`
|
|
2
|
+
|
|
3
|
+
## π‘ concept
|
|
4
|
+
a use case describes how a user interacts with a system to achieve a specific goal, detailing the steps, actors, and system responses involved in the interaction.
|
|
5
|
+
|
|
6
|
+
## β question
|
|
7
|
+
> what is a narrative example of a use case?
|
|
8
|
+
|
|
9
|
+
## π narrative: ordering dinner on an app
|
|
10
|
+
|
|
11
|
+
### π.π what
|
|
12
|
+
|
|
13
|
+
> what is the story of ordering dinner on an app?
|
|
14
|
+
|
|
15
|
+
emma has just finished a long day at work and doesnβt feel like cooking. she opens her favorite food delivery app on her phone, browses local restaurants, and chooses a thai place she likes. after customizing her pad thai with no peanuts, she taps βorder now.β
|
|
16
|
+
|
|
17
|
+
- the **system** processes her payment and confirms the order.
|
|
18
|
+
- the **restaurant** receives the request and begins cooking.
|
|
19
|
+
- a **courier** is assigned and notified through the app.
|
|
20
|
+
- emma gets real-time updates and watches the courierβs location as the delivery approaches.
|
|
21
|
+
- finally, the courier rings her doorbell and hands her dinner, just as the app marks the order complete.
|
|
22
|
+
|
|
23
|
+
### π.π how
|
|
24
|
+
|
|
25
|
+
> how does this narrative embody a use case?
|
|
26
|
+
|
|
27
|
+
this narrative demonstrates a use case because it shows:
|
|
28
|
+
|
|
29
|
+
- **actors**: emma (customer), the app (system), the restaurant, and the courier.
|
|
30
|
+
- **goal**: emmaβs objective of getting a meal delivered.
|
|
31
|
+
- **steps**: the sequence of interactionsβfrom browsing and ordering to cooking, delivery, and confirmation.
|
|
32
|
+
- **system responses**: payment processing, status updates, and delivery tracking that support each step.
|
|
33
|
+
|
|
34
|
+
by telling a story from the userβs perspective, the narrative highlights the flow of interactions that define a use case, making the abstract concept tangible and relatable.
|
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
# .brief.demo: `use case` via `walkthrough` = `booking a hotel room online`
|
|
2
|
+
|
|
3
|
+
## π‘ concept
|
|
4
|
+
a use case describes how a user interacts with a system to achieve a specific goal, detailing the steps, actors, and system responses involved in the interaction.
|
|
5
|
+
|
|
6
|
+
## β question
|
|
7
|
+
> what is a walkthrough example of a use case?
|
|
8
|
+
|
|
9
|
+
## π walkthrough: booking a hotel room online
|
|
10
|
+
|
|
11
|
+
### π.π what
|
|
12
|
+
|
|
13
|
+
> what is the walkthrough of booking a hotel room?
|
|
14
|
+
|
|
15
|
+
a customer wants to reserve a hotel stay through a booking website. this walkthrough guides step by step through the interaction from start to finish.
|
|
16
|
+
|
|
17
|
+
1. **open system**
|
|
18
|
+
- user navigates to the hotel booking website.
|
|
19
|
+
- *system response:* homepage loads with search bar.
|
|
20
|
+
2. **search hotels**
|
|
21
|
+
- user enters destination, dates, and guest count.
|
|
22
|
+
- *system response:* list of available hotels appears.
|
|
23
|
+
3. **select hotel**
|
|
24
|
+
- user browses and chooses a hotel.
|
|
25
|
+
- *system response:* details page shows amenities, price, and photos.
|
|
26
|
+
4. **choose room**
|
|
27
|
+
- user selects a room type.
|
|
28
|
+
- *system response:* room availability and price confirmed.
|
|
29
|
+
5. **enter details**
|
|
30
|
+
- user provides guest information and payment method.
|
|
31
|
+
- *system response:* form validates input and displays order summary.
|
|
32
|
+
6. **confirm booking**
|
|
33
|
+
- user clicks βbook now.β
|
|
34
|
+
- *system response:* confirmation page with reservation number and email receipt.
|
|
35
|
+
|
|
36
|
+
### π.π how
|
|
37
|
+
|
|
38
|
+
> how is this a walkthrough of a use case?
|
|
39
|
+
|
|
40
|
+
this walkthrough shows the **structured sequence** of steps and responses:
|
|
41
|
+
|
|
42
|
+
- **actors**: user and system are clearly identified at each stage.
|
|
43
|
+
- **goal orientation**: every step moves toward the outcomeβsuccessfully booking a room.
|
|
44
|
+
- **interaction clarity**: system responses are paired with user actions, demonstrating the back-and-forth flow.
|
|
45
|
+
- **step-by-step detail**: breaking the process into checkpoints makes the use case easy to follow and replicate.
|
|
46
|
+
|
|
47
|
+
the walkthrough method highlights the **procedural nature** of a use case, showing how user actions trigger system behavior until the goal is achieved.
|
package/dist/roles/thinker/briefs/librarian.tactics/[brief].verbiage.outline.over.narrative.md
ADDED
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
# π§© .brief: `brief.article.format.outline`
|
|
2
|
+
|
|
3
|
+
## .what
|
|
4
|
+
**`brief.article.format.outline`** specifies the preference for writing **[brief][article]**s in **outline format** rather than paragraph format,
|
|
5
|
+
in order to **maximize signal-to-noise ratio** β ensuring the reader receives the **most relevant information** with the **least distraction**.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## π― purpose
|
|
10
|
+
- prioritize **information density** over narrative flow
|
|
11
|
+
- enable **rapid scanning** and **selective focus** on relevant points
|
|
12
|
+
- minimize **filler language**, rhetorical padding, and connective prose that dilute clarity
|
|
13
|
+
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
## π rationale
|
|
17
|
+
### 1. higher signal density
|
|
18
|
+
- each point stands alone, stripped to its essential statement
|
|
19
|
+
- no dependency on surrounding sentences for meaning
|
|
20
|
+
|
|
21
|
+
### 2. lower cognitive noise
|
|
22
|
+
- reduced verbal clutter, fewer transitions
|
|
23
|
+
- visual separation between concepts lowers mental parsing cost
|
|
24
|
+
|
|
25
|
+
### 3. faster scanning & retrieval
|
|
26
|
+
- indentation and bullet hierarchy serve as immediate visual anchors
|
|
27
|
+
- enables βjump-to-pointβ reading without loss of context
|
|
28
|
+
|
|
29
|
+
### 4. explicit structure
|
|
30
|
+
- hierarchy is visible, not inferred
|
|
31
|
+
- easier to map relationships between concepts at a glance
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## π comparison
|
|
36
|
+
| factor | outline format | paragraph format |
|
|
37
|
+
|-------------------------|----------------|------------------|
|
|
38
|
+
| signal density | **high** | medium |
|
|
39
|
+
| noise suppression | **strong** | weaker |
|
|
40
|
+
| scan speed | **fast** | slower |
|
|
41
|
+
| structure visibility | **explicit** | implicit |
|
|
42
|
+
| nuance capacity | lower | higher |
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
## π usage guidance
|
|
47
|
+
- default to outline format for all `[brief][article]`s
|
|
48
|
+
- use paragraph sub-sections **only** when nuance or rhetorical flow is essential
|
|
49
|
+
- keep bullet points **single-idea only**; avoid compound sentences in bullets
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
## π note
|
|
54
|
+
this preference is **format-level**, not **content-level** β it shapes **presentation**, not **what is included**.
|
|
55
|
+
the core content of a [brief] remains the same regardless of format; the outline format simply transmits it **more cleanly and quickly**.
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# π¦ definition of logistics
|
|
2
|
+
|
|
3
|
+
## core meaning
|
|
4
|
+
logistics is the organized process of **planning, implementing, and controlling the movement and storage of goods, services, and information** from their point of origin to their point of consumption.
|
|
5
|
+
|
|
6
|
+
## key functions
|
|
7
|
+
- **transportation** β moving goods by road, rail, sea, air, or pipelines
|
|
8
|
+
- **warehousing** β storing goods until they are needed
|
|
9
|
+
- **inventory management** β balancing supply with demand to avoid shortages or surpluses
|
|
10
|
+
- **packaging & handling** β preparing items for safe and efficient movement
|
|
11
|
+
- **information flow** β tracking shipments, scheduling, and coordinating operations
|
|
12
|
+
- **distribution** β delivering goods to customers or retail locations
|
|
13
|
+
|
|
14
|
+
## scope
|
|
15
|
+
- **business / supply chain** β logistics ensures that materials, parts, and products are in the right place, at the right time, in the right quantity, and at the lowest possible cost
|
|
16
|
+
- **military** β originally, the term referred to supplying and moving troops, equipment, and weapons
|
|
17
|
+
- **modern extensions** β covers not only physical goods but also digital and service logistics (e.g., cloud computing infrastructure, health care logistics)
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
π in short: logistics = *the art and science of getting things where they need to be, when they need to be there, as efficiently as possible.*
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
# π§Ύ definition of logistics in the scope of information
|
|
2
|
+
|
|
3
|
+
## core meaning
|
|
4
|
+
**information logistics** is the discipline of **planning, implementing, and controlling the flow of information** so that the right data reaches the right people or systems at the right time, in the right form, and with the right quality.
|
|
5
|
+
|
|
6
|
+
## key functions
|
|
7
|
+
- **collection** β gathering information from multiple sources (sensors, databases, users, external feeds)
|
|
8
|
+
- **processing & transformation** β cleaning, enriching, and converting raw data into usable formats
|
|
9
|
+
- **storage & retrieval** β keeping information organized in databases, files, or knowledge systems for timely access
|
|
10
|
+
- **transmission** β distributing information efficiently across networks, devices, or teams
|
|
11
|
+
- **presentation** β tailoring information into forms suitable for human or machine consumption (dashboards, APIs, reports)
|
|
12
|
+
- **tracking & feedback** β monitoring flows to ensure accuracy, timeliness, and relevance
|
|
13
|
+
|
|
14
|
+
## scope
|
|
15
|
+
- **business intelligence** β ensuring decision-makers have up-to-date, relevant data
|
|
16
|
+
- **it systems** β designing infrastructures for reliable data pipelines, synchronization, and delivery
|
|
17
|
+
- **knowledge management** β managing documents, messages, and records as efficiently as goods in a supply chain
|
|
18
|
+
- **digital services** β streaming platforms, cloud systems, and IoT all rely on information logistics for real-time performance
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
π in short: **information logistics** = *treating data like cargo β moving, storing, and delivering it so that it arrives at its destination in the most useful way possible.*
|