{
  "schema_version": "1.1",
  "id": "s9:https://github.com/shy3130/tick-stock-panel",
  "slug": "tick-stock-panel-1hccxyw",
  "url": "https://feed7.dev/p/tick-stock-panel-1hccxyw",
  "title": "shy3130/tick-stock-panel",
  "why_included": "Tick Stock Panel is a self-hosted A-share research stack with screening, backtesting, monitoring, and an AI assistant whose 18 read-only tools expose auditable data calls.",
  "summary": "Tick Stock Panel packages A-share screening, monitoring, and backtesting in a self-hosted Docker app. It includes **25 strategies**, computes **68 indicator and signal columns**, and gives its assistant **18 read-only tools** with inspectable call parameters, timing, and result summaries.",
  "practical_implication": "Agent builders can study its fail-closed tool access, visible tool traces, local Parquet storage, and extension model: backend and frontend modules are discovered through isolated directories and can be removed without changing core files. Data-source capabilities are routed independently so providers can change without altering metric or backtest conventions.",
  "agent_context": "Tick Stock Panel packages A-share screening, monitoring, and backtesting in a self-hosted Docker app. It includes **25 strategies**, computes **68 indicator and signal columns**, and gives its assistant **18 read-only tools** with inspectable call parameters, timing, and result summaries.\n\nAgent builders can study its fail-closed tool access, visible tool traces, local Parquet storage, and extension model: backend and frontend modules are discovered through isolated directories and can be removed without changing core files. Data-source capabilities are routed independently so providers can change without altering metric or backtest conventions.\n\nIt is a personal open-source research project, not trading or recommendation software. Some data sources require separate API keys, the packaged image omits certain plugins, and Codex CLI mode mounts local credentials read-only and should be used only on a trusted machine.",
  "source": {
    "name": "GitHub",
    "url": "https://github.com/shy3130/tick-stock-panel",
    "published_at": null
  },
  "source_class": "tool",
  "content_type": "GitHub Repo",
  "layer": "tools",
  "domains": [
    "data",
    "coding"
  ],
  "topics": [
    "tool-use",
    "dev-ux",
    "context-engineering"
  ],
  "verification": {
    "status": "needs_review",
    "label": "Needs Review",
    "method": "unverified",
    "verified_at": null
  },
  "uncertainty": [
    "It is a personal open-source research project, not trading or recommendation software. Some data sources require separate API keys, the packaged image omits certain plugins, and Codex CLI mode mounts local credentials read-only and should be used only on a trusted machine."
  ],
  "connected_context": {
    "meaning": "This is a concrete domain-agent implementation of bounded, inspectable tooling: read-only assistant actions, visible traces, stable local data conventions, and removable modules constrain behavior without hiding extensibility. It supports structured domain interfaces over generic tool access, while its personal-project status and credential assumptions limit how far the pattern can be generalized to production or multi-user systems.",
    "corpus_size": 878,
    "generated_at": "2026-09-26T09:04:38.567Z",
    "connections": [
      {
        "title": "An Empirical Study of Harness Design for Coding Agents",
        "source_name": "arXiv",
        "source_url": "https://arxiv.org/abs/2609.20804v1",
        "feed7_url": "https://feed7.dev/p/2609-20804v1-17ecr62",
        "reason": "The app demonstrates an elaborate domain toolset, while the harness study cautions that such tooling must be justified per model and budget rather than assumed to outperform simpler interfaces."
      },
      {
        "title": "The Next Game Engine Won't Have a Manual — Arturo Nunez, Nereu",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=VBCDhRrvlYo",
        "feed7_url": "https://feed7.dev/p/the-next-game-engine-won-t-have-a-manual-arturo-nunez-nereu-1v4vd0y",
        "reason": "Its stable metric, backtest, and provider conventions exemplify the domain-native vocabulary that Nereu argues agents need instead of generated integration glue."
      },
      {
        "title": "MCP Apps: Give the Model Data, Give the User a UI — Dustin Mihalik, Indeed",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=lbaXnx0KLA8",
        "feed7_url": "https://feed7.dev/p/mcp-apps-give-the-model-data-give-the-user-a-ui-dustin-mihalik-indeed-1gi9v8k",
        "reason": "Its separate backend and frontend modules align with the recommendation to keep data exploration independent from rendering, preserving inspectable tool work before presentation."
      },
      {
        "title": "Your company brain will leak secrets: how we stopped it for big banks — Tanmai Gopal, PromptQL",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=0uC6u0lJJl4",
        "feed7_url": "https://feed7.dev/p/your-company-brain-will-leak-secrets-how-we-stopped-it-for-big-banks-tan-1xrm58g",
        "reason": "Read-only tools and read-only credential mounts reinforce bounded access, but the shared-memory guidance shows that production multi-user use would additionally require per-request identity and user-scoped authorization."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": null,
  "modified_at": null,
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/tick-stock-panel-1hccxyw",
    "json": "https://feed7.dev/p/tick-stock-panel-1hccxyw.json",
    "markdown": "https://feed7.dev/p/tick-stock-panel-1hccxyw.md"
  }
}