Person/codekiln/GitHub/logseq-gardener/Analysis/Fable
Namespace — browse the pages below.
66 Linked References
Hierarchy
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120658 ET A Logseq-aware git merge driver before a CRDT
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120658 ET Measure the corpus before designing the cache
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120658 ET One tool carries four names and two of them collide
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120658 ET Pick the parser first and let the language follow
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120658 ET Publish by exporting plain Markdown to a standard site generator
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120658 ET Ship the agent CLI first and let the LSP inherit the index
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120658 ET Smaller fixes to the Brief and Goals pages
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120933 ET Agents calling the CLI justify a persistent cache on a small garden
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120933 ET Answer page existence with a typed result and an exit code
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120933 ET Call the impact command garden diff and run it where the link checker runs
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120933 ET Expand embeds before evaluating queries in the publisher
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120933 ET Give each checkout its own cache and share parsed text later
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120933 ET Use Logseq's own graph-parser as the oracle and require a byte-identical round trip
- PersoncodekilnGitHublogseq-gardenerAnalysisFable2609120933 ET Where my plan agrees with Astra's proposal and where it departs