mantoshkumar1 / mantoshkumar1/mantoshkumar1.github.io

Fix Ask Mantosh knowledge-document count drift in SYSTEM_STATE.md

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1
Forks
0
Avg merge
13m
Merged PRs (30d)
2

Description

Problem

docs/SYSTEM_STATE.md currently describes 18 public Ask Mantosh documents in the published inventory, but the Known limits section says 17 public knowledge documents are indexed.

The canonical production-state document should not contain conflicting inventory counts.

Scope

  • Determine the actual indexed/public knowledge-document count.
  • Update docs/SYSTEM_STATE.md so all references agree.
  • Check whether an existing audit can verify this count automatically.
  • If not, add a deterministic documentation/content audit so future count drift fails CI.

Acceptance criteria

  • One authoritative count is used throughout docs/SYSTEM_STATE.md.
  • The count matches the current public knowledge corpus.
  • CI or an existing deterministic audit detects future drift where practical.
  • npm run verify passes.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/SYSTEM_STATE.md and determine the actual public knowledge-document count from the current corpus. Check the existing audits and the npm run verify entry point to see whether deterministic count validation already exists; update the document and add or extend an audit so the acceptance criteria and verification command pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
ci-cd, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.