Skip to content

Commit 3e4c747

Browse files
Update BITCODE_SPEC_V38_NOTES.md
1 parent d0652b9 commit 3e4c747

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

BITCODE_SPEC_V38_NOTES.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,19 @@
11
V38 should ensure PTRR agents' steps use FailsafeGenerations above (sans tools) ThricifiedGenerations (RJS per Failsafe (context preparation, large input handling, large output handling - each RJS (Thriceified) within them)
22

3-
Thricification is the lowest-level inference call chaining (final prompt regsitry resolutions (above call chain) to compose final form, inteprolations formatted etc.). Failsafes are also generic inference chains but delegate their internal infer down (again, in the case of PTRR agent implementations) to Thricified
3+
Thricification is the lowest-level inference call chaining (final prompt regsitry resolutions (above call chain) to compose final form, interpolations formatted etc.). Failsafes are also generic inference chains but delegate their internal infer down (again, in the case of PTRR agent implementations) to Thricified
44

55
Ensure pipeline execution agents inference call stack is completed correctly (prompt registries and final compositions and interpolations, prompt contents and context expectations, generation implementations (Failsafes, Thricifieds) from phase->agents(PTRR)->steps->...etc.
66

7-
V38 should also close all inference edges such as total promptpart/prompt/template implementations to commercial-readiness for all inference usages (both reading pipelines (phase, agebt, step, geberations), other interfaces such as conversations, tool definition prompts) both base/primitive layers ("an agent's step...") and specific implementations ("this agent's step...") fully utlizing the registry, prompt, execution, (and other) primitives to their maximum potential
7+
V38 should also close all inference edges such as total promptpart/prompt/template implementations to commercial-readiness for all inference usages (both reading pipelines (phase, agent, step, generations), other interfaces such as conversations, tool definition prompts) both base/primitive layers ("an agent's step...") and specific implementations ("this agent's step...") fully utlizing the registry, prompt, execution, (and other) primitives to their maximum potential
88

9-
V38 is inference focused entirely to correct errors and gaps in implementations, fully utilize the inference call stack (and other) commeecial infrastructure abstractions, architectures, and patterns now having Bitcode to a significantly more comprehensive production-readiness stage.
9+
V38 is inference focused entirely to correct errors and gaps in implementations, fully utilize the inference call stack (and other) commercial infrastructure abstractions, architectures, and patterns now having Bitcode to a significantly more comprehensive production-readiness stage.
1010

1111
full and proper Failsafe and Thricified usages, full and proper pipeline execution implementations, full and proper PTRR agent, full and proper use of Tool with their doc-comment method of definitions (always in all cases composed/interpolated/injected fully properly at the final (lowest) inference call stack point), ensure all interpolations/templating is correct wherever in call stack, full and proper execution context (through execution ancestry state-stack) is written/read/prepared(failsafe(s))/interpolated/maintained full and proper through executions its inferences, etc. etc.
1212

13-
finish implementing prompt and promptpart benchamrking system (in progress) fully (semantically divided promptparts, complete prompts, both benchmarkable) and create initial benchnarks for all parts and prompts
13+
finish implementing prompt and promptpart benchmarking system (in progress) fully (semantically divided promptparts, complete prompts, both benchmarkable) and create initial benchmarks for all parts and prompts
1414

1515
robustly integrating with previous telemetry (and other) inference empowering effort
1616

17+
in addition to V38's inference focus, fits-finding/depository-searching (tools, primitive utilities) should also be completed correctly as queries etc. are inference derived. ensuring that reliable embeddings for source, measurements, metadata, query synthesis, etc. provide rich searchability during fits-finding's pipeline's search moments, the results are properfully gathered, ranked, utilized for AP synthesis, all with prompt inference driving multi-faceted search approaches to gather optimally large option set to consider to synthesis optimal asset packs. using tools over vector search, using llama index pinecone OAI embeddings custom etc. multiple where appropriate to ensure reads reach fully throughout the Bitcode depository reliably to drive optimal intelligence fed into AP synthesis (and of course those fits carrying through to compensations (AP's distribute fees to fitters-as-contributors, etc.). Fits-finding's inner search tooling (prompts, primitive utility packages, multi-faceted approach), execution algorithms (agent steps, context organization, etc.) is a sub-primary yet also critical second focus of V38 coupled-tighly with all the inference that operates on/with/before(in preparation)/after Bitcode depository fits.
18+
1719
ultimately, Bitcode's ability to maximize inference intelligence provides the technical-intelligence measurements/labellings that allow for realibly positive and mutually beneficial experience if depositing (selling) and reading (buying) precise technical intelligence (BTD/AssetPacks)

0 commit comments

Comments
 (0)