Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Mississippi Code of 1972 (Annotated) — state statutes by citation, and a chapter list by title.…
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
PIPEWORX_API_KEY비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://gateway.pipeworx.io/mississippi-code/mcpClaude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"mississippi-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-mississippi-code"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add --transport http mississippi-code https://gateway.pipeworx.io/mississippi-code/mcpclaude mcp add mississippi-code --env PIPEWORX_API_KEY=your-value -- npx -y @pipeworx/mcp-mississippi-code실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"mississippi-code": {
"url": "https://gateway.pipeworx.io/mississippi-code/mcp"
}
}
}프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"mississippi-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-mississippi-code"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"mississippi-code": {
"type": "http",
"url": "https://gateway.pipeworx.io/mississippi-code/mcp"
}
}
}프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"mississippi-code": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-mississippi-code"
],
"env": {
"PIPEWORX_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://gateway.pipeworx.io/mississippi-code/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
ask_pipeworxPREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au
ask_pipeworx_betaBeta version of ask_pipeworx: identical universal router (same 7,176 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so
ask_pipeworx_groundedHallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,176 across 1863 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati
search_withinSemantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th
deep_researchACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1863 STRUCTURED data sources (SEC filings,
discover_toolsFind tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est
resolve_entity"What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re
compare_entities"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing
subscribeCreate a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o
unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
recent_alertsPull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).
entity_profile"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha
recent_changes"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s
validate_claim"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f
company_factsTYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe
company_register_searchSearch the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CNPJ, or an LEI. Use this when you want
scan_dependencyComposite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular
bet_researchResearch a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett
polymarket_arbitrageFind arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev
polymarket_edgesScan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme
polymarket_kalshi_spreadCross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s
polymarket_fill_riskRealizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di
polymarket_edge_trackerEdge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d
kalshi_weather_edgePrices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob
resolution_auditExtract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P
resolution_diffField-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi
release_calendar_marketsJOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c
prediction_calibrationREALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it
updown_venue_compareThe same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as
updown_divergence_rateHow often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:
archive_evidenceWhat did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy
archive_compareWhat changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b
research_rowClaygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in
classify_rowCheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e
pipeworx_trendingWhat other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice
suggest_questionsWhat can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e
generate_llms_txtGenerate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si
ai_visibility_checkProbe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe
scan_competitor_ai_presenceCompare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co
pipeworx_feedbackTell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor
rememberSave data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v
recallRetrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous
forgetDelete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
ms_code_sectionGet the text of a section of the Mississippi Code of 1972 (Annotated) — Mississippi state law — by citation. "97-3-19" is homicide/murder; "89-8-19" is a landlord's duty to return a security deposit. Accepts natural forms: "97-3-19", "Miss. Code Ann. § 97-3-19", "Section 97-3-19"
ms_code_chaptersList the chapters within a title of the Mississippi Code of 1972, by title number ("97" is Crimes, "89" is Real and Personal Property, "27" is Taxation and Finance). Use this to browse a title when you do not have an exact section citation. Returns every chapter heading and numbe
ms_code_searchSearch the Mississippi Code of 1972 BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". Matches against every section's official CATCHLINE across the whole Code (not full statutory body text — there is no full-text sea
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 pipeworx-io 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
252ms 만에 응답(HTTP 200)
로그인 필요 없음
도구 설명 47개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: PIPEWORX_API_KEY
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.1)은 4일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Systemdox
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Mississippi Code of 1972 (Annotated) — section lookup by citation, chapter browsing by title, and topic/keyword search over official catchlines. Fleet #2883. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
ms_code_section(citation) — the text of a section by citation ("97-3-19", "Miss. Code Ann. § 89-8-19", "Section 97-3-19"). Returns the catchline, the operative statutory text, the HISTORY: line, and Joint Legislative Committee / Amendment / Cross-Reference notes when present, AND a later_acts overlay — every act this pack's own crawl of Mississippi's signed-bill text shows touching this exact citation since the 2020-07-08 snapshot (fleet #2915, see "The overlay" below). Case-law (JUDICIAL DECISIONS) annotations are deliberately excluded — they can run to hundreds of citations per section and are not what a caller asking "what does this statute say" wants back.ms_code_chapters(title) — every chapter heading and number within a title (97 is Crimes, 89 is Real and Personal Property), for browsing when you don't have an exact citation.ms_code_search(query, limit?) — topic/keyword search over every section's official CATCHLINE (not full statutory body text — see "Why no full-text search" below). Matches like North Dakota's nd_search: IDF- weighted word overlap over a baked index, not a live upstream call.Keyless. No signup, no login, on either side of the call.
The official LexisNexis-hosted Code (lexisnexis.com/hottopics/mscode, linked from the Secretary of State's own site) sits behind a Cloudflare managed challenge — confirmed live: every direct request gets a "Just a moment..." interstitial page, HTTP 403, no statute text. The two common free third-party renderings, law.justia.com and codes.findlaw.com, sit behind the exact same Cloudflare challenge (confirmed live, identical "Just a moment..." body) — this is not a Lexis-specific wall, it's a Cloudflare bot-check in front of three different vendors' copies of the same text, so there is no "try a different mirror of the search UI" move here.
archive.org/download/gov.ms.code.ann.2018), "in the public domain, NO RIGHTS RESERVED" per that repo's own README. One title per HTML page (gov.ms.code.title.{NN}.html, title zero-padded to 2 digits — Mississippi titles are odd numbers 1-99), fetched LIVE per ms_code_section / ms_code_chapters call — this pack proxies it, it does not ship a copy of the Code in the repo (mirror-needs-grant-proxy-does-not in the Pipeworx CLAUDE.md licence section).The underlying statutory TEXT is public law regardless of what any publisher's licence says about its own rendering — enacted law carries no copyright (*Banks v. Manchester*, 128 U.S. 244 (1888); *Veeck v. SBCCI*, 293 F.3d 791 (5th Cir. 2002) (en banc)).
THE HONEST LIMIT. This source is Release 78, released 2020-07-08, generated from the Code's 2018 printed RTF volumes. It is a static snapshot, not a continuously updated feed — amendments enacted in the 2021 through 2026 Regular Sessions are not reflected. Every response carries current_through and data_as_of: "2020-07-08" rather than defaulting to "now", which would misrepresent six-year-old text as current law. For anything enacted after mid-2020, verify against the official LexisNexis- hosted Code or contact the Joint Legislative Committee on Compilation, Revision and Publication of Legislation (Miss. Code Ann. §§ 1-1-101 to 1-1-111).
Title 79 (Corporations, Associations, and Partnerships) cannot be looked up section-by-section. Checked live across all 50 titles (2026-10-09): every other title's section-heading tag (h3, id attribute formatted t{title}c{chapter}s{citation}) carries that id — 27,688 sections total — but Title 79's ~700 section headings are all bare h3 tags with no id at all (reused instead for unrelated asides like editor's notes), and the internal citation anchor it links to (e.g. href="#t79c01s79-1-1") is dangling — no element in that title's document carries that id. ms_code_section names this explicitly (reason: "title_markup_unsupported") rather than returning an indistinguishable citation_not_found. ms_code_chapters still works for Title 79 (its chapter table of contents is intact); only section-level text extraction is blocked.
Bruce kept ms_code_section on the frozen 2020-07-08 snapshot ("we'll need to figure something out") rather than chase a fully reconciled current code — the same ruling arkansas-code's overlay (fleet #2906) shipped under. This overlay is the cheapest honest improvement on top of that decision — design and measurements in docs/current-statute-routes.md (#2902).
Unlike Arkansas, Mississippi's legislature publishes no ready-made citation-to-act index. billstatus.ls.state.ms.us has bill-status pages and signed-bill text, not a "sections amended" lookup — so this overlay is home-built: crawl every enacted bill's own signed text and parse the boilerplate every Mississippi amending bill uses, "SECTION N. Section , Mississippi Code of 1972, is amended as follows:" (also "is created"/"shall be codified as Section , Mississippi Code of 1972"/"is repealed"/"is brought forward as follows"/"is reenacted as follows" — a sunset-renewal verb folded into the "amended" bucket since it touches the citation the same way).
The rule: never rewrite the snapshot `text`. Only ever ADD a dated, linked list beside it, explicitly labelled as not merged. ms_code_section's response carries:
later_acts — one entry per act that touched this exact citation since the snapshot date: chapter (the Session Laws chapter number, from the bill's own history record — null if not yet assigned), session (human-readable, e.g. "2025 Regular Session"), verb (amended/created/repealed/brought_forward), range_to (non-null only when the act touched a Sections X through Y RANGE rather than one citation — see "Ranges" below), link (the bill's own signed-text page), bill (the measure number), source: "billstatus", and merged: false. Empty ([]) means the overlay shows no later act for this citation across every session checked — not that the overlay failed to load (a missing/malformed KV index throws loudly instead, same as ms_code_search's catchline index).sessions_checked — every session the overlay covers, named even when later_acts is empty, so a caller can tell "nothing changed" from "we didn't check."later_acts_data_as_of — when the overlay was last baked.Ranges. A clause like "Sections 75-15-1 through 75-15-35, Mississippi Code of 1972, ... is hereby repealed" is kept as ONE row carrying both endpoints rather than this pack fabricating every citation in between (some of which may not exist — Mississippi section numbering is not always contiguous, confirmed live: one 2025 bill reenacted only the ODD-numbered sections of a chapter). ms_code_section matches a queried citation against a range by numeric containment on the trailing segment, with the same title-chapter prefix — not by this script guessing which numbers the range actually contains.
What is deliberately NOT indexed (measured on a 100-bill live sample, see "Measured coverage" below): a clause amending an uncodified SESSION LAW ("Section 7, Chapter 467, Laws of 2019, ... is amended") never mentions "the Mississippi Code of 1972" and is correctly excluded — it never touches a Code citation. A clause creating a brand-new section that has not yet been assigned a final citation ("Section N of this act shall be codified in Chapter X, Title Y, Mississippi Code of 1972") is excluded too — there is nothing to key a row on until the compiler assigns the number, which this source does not do.
A section not found in the Release-78 snapshot but present in the overlay is flagged specially: ms_code_section's found: false response carries later_acts_if_created — if this pack's own crawl shows acts against a citation that does not exist in the 2020 snapshot, that is a signal the section may have been CREATED after the snapshot date, not necessarily a bad citation.
Measured coverage (2026-10-10, 100 real enacted bills sampled evenly across the 2021-2025 Regular Sessions): 208 "SECTION N." clauses named "Mississippi Code of 1972" near their start; 207 parsed into a verb (99.5%). The one miss ("...Section 25-11-415, Mississippi Code of 1972, which provides that...") is a descriptive cross-reference inside an appropriations bill, not an amending clause — genuinely unparseable because it never uses one of the five recognized verbs, reported to stderr by scripts/bake-later-acts.mjs (--report-unparsed also emits it as a // UNPARSED_REPORT: comment in the generated file) rather than silently dropped. The full production run (every session discovered since 2021, not just the 100-bill sample) is the number actually baked into MS_LATER_ACTS below.
Source: billstatus.ls.state.ms.us — keyless, no bot wall, confirmed live 2026-10-10 (HTTP 200, plain HTML/XML, no JS rendering required). We are proxying the Legislature's own public bill-status site per request during the bake, not redistributing a copyrighted rendering — the statutory text itself carries no copyright (*Banks v. Manchester*; *Veeck v. SBCCI*, both cited above), and the bill text is the Legislature's own public record.
For Tennessee (next): reuse, don't re-derive. What carries over directly from this build (same shape Arkansas handed to this one): the response shape (later_acts/sessions_checked/ later_acts_merged_into_text: false/the "never rewrite text" rule), the baked-index + KV injection pattern (append new exports to the SAME src/ -index-data.ts file the catchline index already uses), the session-discovery-over-hardcoding trick (read the live session list rather than a fixed one), and the scripts/bake-later-acts.mjs -> scripts/ -later-acts-refresh.yml shape for the refresh workflow. Tennessee, like Mississippi, has no official citation index either (per docs/current-statute-routes.md) — its bill text is PDF (capitol.tn.gov), not HTML, so its boilerplate parser will need pdftotext rather than this pack's HTML-stripping, but the regex shape of the boilerplate itself is the same "SECTION N. Tennessee Code Annotated, Section X, is amended..." pattern.
src/ms-index-data.ts carries TWO independently-baked tables, both injected from KV via workers/gateway/src/pack-baked-indexes.json as one combined _bakedIndex object rather than bundled (fleet #2754: a value-imported multi-MB table loads into every gateway isolate whether or not it ever serves this pack):
MS_SECTIONS — ms_code_search's catchline index, 27,688 rows across the 49 titles whose markup supports it (see "Title 79" above). Rebuild with node scripts/bake-index.mjs > src/ms-index-data.ts (OVERWRITES the file — see below). Re-run only if unicourt.github.io/cic-code-ms publishes a release newer than 78.MS_LATER_ACTS/MS_LATER_ACTS_SESSIONS_CHECKED — ms_code_section's overlay index (fleet #2915), built by crawling and parsing billstatus.ls.state.ms.us's own signed-bill text (no official index exists). Rebuild with node scripts/bake-later-acts.mjs >> src/ms-index-data.ts (APPENDS). Re-run after every Missi앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요