labels: training, experimentaiton
feel like maybe I'll be more inspired here if I put the ideas in one place.
I also like that PR/FAQ thing I saw the other day where someone was writing reviews for SD finetunes they hadn't yet trained or something like that.
anyway, I was inspired to make this now for the following idea:
- document-to-mindmap
- summarize a document into a graphical summary saved as a text file. graphical summary document GSD.
- needs to be parameterizable as a text format so we can just use an LLM to generate these.
- construct a procedure for growing this representation that pushes in "missing" notes
--
- Django
- FastAPI
- huggingface/transformers
- huggingface/diffusers
- numpy
- scipy
- pandas
- sklearn
- pytorch
- pytorch-lightning
- Gin
- terraform
- kubernetes
- knative
- prometheus
- etcd
- helm
- argoCD
- docker
- singularity
- slurm
- TVTropes
- worldbuilding.stackexchange
- subreddits? There must be loads of subreddits that would be good here.
- /r/askhistorians
- Some sort of public crowd-sourced CliffsNotes? That has to be a thing, right?
- Generated brainstorming dialogues
- Real Event -> summary -> elevator pitch -> hallucination -> TVTropes -> characters -> TVTropes -> story arcs
- inspiration -> tropes -> elevator pitch -> who/what/where/when/why/how -> criticize proposal as "facile" -> add complexity to characters motivations -> adjust theme
- elevator pitch from invested perspective
- topic -> context -> context from alternative perspectives -> guide towards target perspective -> adjacent topics -> Synthesize -> TOC -> coarse-to-fine
- foreach
- more
- topic -> isolate piece of response -> "elaborate" -> ...
- pseudocode
- user stories and action items
- collaborative brainstorming
- https://chat.openai.com/c/b5c20579-f574-43d0-b31a-6e0b9ce0a3fc
- https://chat.openai.com/c/deec108c-f45f-46a7-bdcd-3ff3a2b4e444
- https://chat.openai.com/c/a416562c-acbf-42f3-afe8-58f8236cd06a
- https://chat.openai.com/c/b925108b-e11f-4f0d-9d6c-82e88347102c
- https://chat.openai.com/c/2dbb6562-9655-464e-b464-410f27ebd49f
- adding notes/comments/type-hints/documentation in-line
- PR/FAQ -> user stories -> test suite -> README/core features tutorial -> skeleton codebase -> prioritize development plan -> pros/cons -> flesh out -> reassess plan -> reassess target userbase -> assess competition and differentiators
- "tell me about ___" -> "> ... \n elaborate"
- corase-to-fine outline -> please expand on ....
- debate between opposing viewpoints
e.g. could recursively utilize a coarse-to-fine strategy to develop multi-resolution outline structures, and use different focused sections of outline as context signal provided to an adaptor module.
this is probably overkill and in-context learning probably accomplishes most of what I want here. but yeah, could finetune a LoRA or something.
with each chunk and level of depth of a document, associate with it a "scratchpad". this can be a single file, or multiple files. should represent considerata relevant to that "local" context. represent doucment as a nested file tree. each level of the tree contains a "content" directory for the actual content, and a "scratch" directory for context documents. as content gets authored, scratch content in adjacent directories can be updated.
document can be accompanied by a log (git log?) documenting change history, and each scratch space can be accompanied by its own respective "to do" list of action items for work that needs to be developed locally, content to be developed, etc.
"you are generating content for ___ textbook in the form of wiki articles. highlight topics and phrases that merit their own articles as hyperlinks, using the following markup syntax: this is an [[inline link]] to another [[article]]. the current article is on the topic: '{article topic}. Begin."
spider to push out more content