Skip to content
K = 0.731
2026.10.17 · Sat

#Anthropic

#Anthropic

Tutorials

Tutorials, hands-on experience, usage tips, prompts and tool how-tos, and in-depth technical explainers.

10/14Wed
  1. AWS Machine Learning Blog63

    Natural language security queries at Orca Security using Amazon Bedrock

    Orca Security partnered with AWS to build Discovery AI on Amazon Bedrock, translating natural language questions into validated Sonar queries across 900+ cloud infrastructure and application models. The architecture combines example retrieval and reranking, relevant schema selection, agentic generation, and validation, with domain experts continuously updating the example bank. Compared with its initial baseline, Orca reports 90 percent lower costs, 93 percent fewer input tokens, and 75 percent lower latency, with response times falling from approximately 60 seconds to 15 seconds.

    Why it matters: The architecture offers a transferable approach to querying large schemas by retrieving validated examples, selecting relevant schema fragments, and feeding validation errors back into generation.

  2. 宝玉 · X81

    Why Anthropic built Scion to replace git for its monorepo

    Drawing on Anthropic’s engineering blog, Baoyu explains why the company replaced git with Scion as daily merged code changes grew from around 2,500 in May to more than 30,000 in September. Scion retrieves files on demand, moves operations to the server, and uses layered caches with hit rates above 99%. Anthropic reports that median agent workspace startup fell from 7.1 minutes to 5.1 seconds, while emphasizing that Scion serves exceptionally large monorepos and is not a general-purpose git replacement.

    Why it matters: The comparison illustrates how assuming continuous server access changes source control architecture, connecting on-demand file retrieval and server-side operations to the infrastructure demands of agent-generated code.

10/13Tue
  1. AWS Machine Learning Blog75

    Build long-horizon agents with Grok 4.7 on Amazon Bedrock

    AWS demonstrates how to build and evaluate a tool-calling agent using Grok 4.7 on Amazon Bedrock, comparing four reasoning effort levels across three synthetic tasks. The agent answered 67 of 72 runs correctly; xhigh achieved 18 of 18, while low achieved 15 of 18 using about an eighth of the output tokens. The guide covers task design, automated grading, production monitoring, and operational controls, noting that these small-scale results are indicative rather than statistically conclusive.

    Why it matters: Tasks with provably unique answers and repeated runs provide a reusable way to compare reasoning effort, while separate correctness and token measurements make the trade-off concrete.

You've reached the end