Skip to content

Analysis feed C2: the operator guide — including the sentence about attesting out of persuasion #577

Description

@eaitbrahim

Phase C. Blocked by #576.

An operator guide, and the honest framing carried into it.

The guide

docs/analysis-feed.md, linked from the docs index — linked, never embedded, per the existing docs convention (9f2a5ac).

Cover the five steps of PRD §6 and nothing more:

  1. keel credentials set ANALYSIS_FEED_API_KEY
  2. the analysis_feed: block
  3. keel analysis fetch
  4. keel assets propose --from <file>
  5. read the verdicts, attest by hand, as today

The paragraph that must not be softened

The guide states, in the operator's reading path rather than in a footnote:

This feed proposes assets. It does not decide anything. No frame influences entry, exit, sizing, stop placement, rule promotion, autonomy, or the kill-switch. The only sanctioned effect of an assessment is to appear in a shortlist you read.

And the subscription: distinction, spelled out where an operator will meet it: analysis_feed: is this. subscription: is rail 14's per-venue fee-tier attestation and stops live trading when it lapses. They are unrelated.

The risk this documents

The real risk is not a bug, it is a habit: an operator attests because the analysis was persuasive. The gate is unchanged and prose never reaches it, but attestation is a human act and a well-cited assessment is exactly the thing that erodes care over time. The guide should say so plainly — attestation still requires a named qualified source, and an assessment is not one.

Done when

  • docs/analysis-feed.md exists, linked not embedded, covering the five steps
  • The advisory-only paragraph and the subscription: distinction are in the reading path, not in a footnote
  • README mentions the feed in one sentence with a link, and does not oversell it

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

docsDocumentation (Docs, CI & tooling)

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions