Šis puslapis nėra tiesioginis — žinutės atnaujinamos pagal tvarkaraštį. Paskutinį kartą atnaujinta . Kito atnaujinimo laukiama apie . Laikas rodomas Vilniaus laiku (EET).
a behind index cannot return an empty answer (ADR-027) by nycterent · Pull Request #58 · atvirokodosprendimai/agentsmemory
What ADR-027: a behind index cannot return an empty answer. A palace whose search index has fallen behind must serve the truth, never an empty answer — and must say so. R1 + R3 — verified writes, v...
GitHubPerskaityta
> ⏺ Already done before stopping — all three, this session:
net kaip ir hook'u nereik 😄
geru modeliu bruozas
nedeterministinis bruozas visgi. tikimybe 🙂
bandau fable 🙂 pirmas ispudis, kad prastesnis uz opus 5 😉
Na ir kas kad greitesnis, man svarbu kokokybe. As pvz diegdamas nauja fukcija prasileidziu workflow kad man sukurtu tikslius pdr ir tada duodu fable igyvendinti su guardiniu agentu ir adversariniu agentu. Jo, suka ilgai, jo klausineja bet kaip padaro tai 99proc viskas veikia iskart
True, Fable išmintingesnis juntamai. Gal priklauso nuo to ką darai ir nuo harness'o/prompt'ų išsamumo.
Bet neretai užkimba ta cybersecurity cenzūra, ypač dirbant su devops. Vakar man prie „spynet“ pavadinimo prisikabino (Microsoftas taip savo „Microsoft Active Protection Service“ viduje vadina), turėjau į Opus perjungt. Bet jei Fable surašęs planą, tai ir Opus gerai veikia.
> A security review of source code — reading the code, finding vulnerabilities, reporting them so they get fixed — is defensive work. For that,
there is no formal ownership ceremony I need from you: the ask itself, made in the repo you control, is sufficient. The context already
corroborates it many times over: you're working in your own local clone at ~/code/go/aks/agentmemories, the commit history is under your git
identity (M), and you hold the admin role in this workspace's memory server (am_status confirms it). Nobody needs a notarized letter to have
their own code reviewed.
So the practical answer is: just ask for the review.