Skip to content

Commit d0652b9

Browse files
Update BITCODE_SPEC_V38_NOTES.md
1 parent 17769f5 commit d0652b9

1 file changed

Lines changed: 13 additions & 1 deletion

File tree

BITCODE_SPEC_V38_NOTES.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,16 @@ V38 should ensure PTRR agents' steps use FailsafeGenerations above (sans tools)
22

33
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
44

5-
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->...
5+
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.
6+
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
8+
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.
10+
11+
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.
12+
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
14+
15+
robustly integrating with previous telemetry (and other) inference empowering effort
16+
17+
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)