idx=9: freeze (20 records) — CSW Industrials Performance Share Award Agreement (no parser changes)#82
idx=9: freeze (20 records) — CSW Industrials Performance Share Award Agreement (no parser changes)#82arthrod wants to merge 1 commit into
Conversation
…Agreement clean under existing parser
CSW Industrials, Inc. Performance Share Award Agreement (Exhibit 10.9).
Form-style stock award agreement with 13 numbered sections, IWW operating
clause, and signature page.
Parse outcome (no code changes required):
- 1 L0 (title "Performance Share Award Agreement"), 15 L1 (preamble grant
block + sections 1-13 + IWW), 4 L2 (sig page fragments)
- pre-title cover ("Exhibit 10.9", "CSW INDUSTRIALS, INC.") dropped by
title-as-root rule
- reconstruction: 98.4% word coverage, 99.4% char ratio
- max level 2, order monotonic
Note: doc2dict groups Section 2's body together with the body text of
Sections 3-13 (because the form HTML chains paragraphs without per-section
container divs). The headers for Sections 3-13 are still detected and
emitted as separate L1 records with empty bodies, so the section structure
is preserved; the body chaining is a doc2dict layout artifact and does not
violate the shape rubric or the 90% reconstruction gate.
|
Mention Blocks like a regular teammate with your question or request: @blocks review this pull request Run |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
CodeAnt AI is reviewing your PR. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📜 Recent review details🧰 Additional context used🔍 Remote MCPBased on my search, I need to note an important limitation: The Stitch tool mentioned in your user requirements is not available in my current toolset, so I cannot fulfill those specific design generation requests. However, I have gathered relevant context about Performance Share Award Agreements that's helpful for reviewing this PR: Summary of FindingsDocument Type Context — Performance Share Award AgreementPerformance Share Award Agreements are designed for granting performance shares to executives of a public company under an equity incentive plan and include key provisions such as grant date, target number of performance shares, performance period, and vesting requirements. The purpose of the performance share award agreement is to clearly describe the goals set forth by the company so that managers can accurately understand what's expected of them. Standard Document StructureTypical Performance Share Award Agreements contain these common sections:
PR Verification AlignmentThe PR documentation indicates the parsed output correctly captured:
This structure aligns with the standard document format found in Performance Share Award Agreements. Limitation NoteRegarding User Requirements: The Stitch tool for design recommendations (create_project, generate_screen_from_text) is not available in my current tools. This PR is data-only and does not require design work, but if design recommendations are needed for related features, they would need to be handled through a different process. 🔇 Additional comments (6)
📝 WalkthroughSummary by CodeRabbit
WalkthroughA new frozen baseline dataset for idx_9 is added, containing a structured "Performance Share Award Agreement" with 20 JSONL segment records, and the state tracking file is updated to register this freeze event with timestamp and record count. ChangesFreeze idx_9 Baseline
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
codeant-ai
Bot
added
the
size:S
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new frozen data file for a Performance Share Award Agreement and updates the global state to include this new index. The review feedback identifies several hierarchical leveling issues that violate the project's structural rubric: the title and preamble need to be consolidated into a single Level 0 record, top-level numbered sections should be reclassified as Level 2, and the signature block components should be corrected to Level 1.
| {"idx": 9, "order": 0, "level": 0, "span": "Performance Share Award Agreement"} | ||
| {"idx": 9, "order": 1, "level": 1, "span": "Date of Grant:\n__________________\nName of Participant:\n___________________\nTarget Number of Performance Shares:\n___________________\nPerformance Period:\nThe period beginning on _____ and ending on _______.\nCSW Industrials, Inc. (the “Company”) hereby awards to _______ (the “Participant”) the target number of shares set forth above which are each equivalent to one Common Share, $0.01 par value per share, of the Company (the “Performance Shares”) pursuant to the CSW Industrials, Inc. Amended and Restated 2015 Equity and Incentive Compensation Plan (the “Plan”). Unless otherwise provided herein, capitalized terms used in this Award Agreement that are defined in the Plan and not defined herein shall have the meanings set forth in the Plan. The terms and conditions of the Performance Shares awarded hereby, to the extent not controlled by the terms and conditions contained in the Plan, are as follows:"} |
There was a problem hiding this comment.
The rubric (defined in level_rubric.md) specifies that Level 0 must consist of exactly one record per index, containing both the agreement title and the preamble paragraph. Currently, the title is at Level 0 (order: 0) and the preamble is at Level 1 (order: 1). These should be consolidated into a single Level 0 record.
| {"idx": 9, "order": 2, "level": 1, "span": "1.No Right to Continued Employee Status Nothing contained in this Award Agreement shall confer upon Participant the right to the continuation of his or her employee status, or to interfere with the right of the Company or any Subsidiary, as applicable, to terminate such relationship"} | ||
| {"idx": 9, "order": 3, "level": 1, "span": "2. Vesting of Performance Shares (a)The Performance Shares awarded hereby are contingently awarded, and the Participant’s vesting in all, or any portion, of the Performance Shares and the issuance of the equivalent number of Common Shares pursuant to Section 3 below, are dependent on the achievement of the Management Objectives set forth in Exhibit A to this Award Agreement and the Participant remaining an employee of the Company or one of its Subsidiaries until the last day of the Performance Period\nSubject to Section 2(c) below, in the event of the Participant’s termination of service from the Company and all Subsidiaries prior to the last day of the Performance Period, the Performance Shares awarded pursuant to this Award Agreement shall be forfeited and cancelled on the date of such termination of service. The Common Shares, if any, that are issued pursuant to this Award Agreement following the end of a Performance Period are subject to the Company’s “Recoupment of Incentive Compensation” policy. (b)Any portion of the Performance Shares that does not vest on the last day of the Performance Period as provided in Section 2(a) above or Section 2(c) below, will be forfeited and cancelled on the last day of the Performance Period.\n(c)Notwithstanding anything contained in this Award Agreement to the contrary, the Performance Shares awarded pursuant to this Award Agreement shall automatically vest as provided in Exhibit A hereto and become issuable as provided in Section 3 below upon the occurrence of any of the following events: (i) a Change in Control, (ii) the Participant’s termination of service from the Company and all Subsidiaries due to his or her Disability or (iii) the Participant’s termination of service from the Company and all Subsidiaries due to his or her death. Additionally, notwithstanding anything contained in this Award Agreement to the contrary, the forfeiture and cancellation of the Performance Shares awarded pursuant to this Award Agreement are subject to the terms and provisions of the Company’s Executive Change in Control and Severance Benefit Plan, dated December 9, 2016, as it may be amended from time to time. “Disability” means the Participant’s inability to engage in any substantial gainful activity by reason of any medically determinable physical or mental impairment which can be expected to result in death or which has lasted or can be expected to last for a continuo us period of not less than twelve (12) months.\nSubject to prior compliance with Section 7 below, the Company will issue the certificate(s) for the equivalent number of Common Shares for all, or the portion, of the Performance Shares awarded to the Participant pursuant to this Award Agreement that have become vested pursuant to Section 2 above as soon as administratively feasible after the end of the Performance Period following written certification by the Committee of the vesting of such Performance Shares and the number of Common Shares that are issuable and no later than the December 31st of the year following the year in which that Performance Period ends in order to ensure that this Performance Share Award and the Plan complies with the specified time of payment requirement of Section 409A(a)(2)(A)(iv) of the Code and Treas. Reg. §§1.409A-3(a)(4) and (d). If, at the time of a Participant’s separation from service (within the meaning of Section 409A of the Code) due to his or her Disability, (i) the Participant is a “specified employee” (within the meaning of Section 409A of the Code and using the identification methodology selected by the Company from time to time) and (ii) the Company makes a good faith determination that the issuance of Common Shares hereunder constitutes deferred compensation (within the meaning of Section 409A of the Code) the payment of which is required to be delayed pursuant to the six-month delay rule set forth in Section 409A of the Code in order to avoid taxes or penalties under Section 409A of the Code, then the Company shall not issue the Common Shares before the fifth business day of the seventh month after such separation from service.\nNeither the Performance Shares awarded pursuant to this Award Agreement nor the right to the Common Shares, if any, which may become issuable pursuant to this Performance Share Award may be (i) sold, assigned, transferred, pledged or otherwise encumbered during the Performance Period or (ii) assignable by operation of law or subject to execution, attachment or similar process. Any attempted sale, assignment, transfer, pledge or other disposition of, and the levy of any execution, attachment or similar process upon, the Performance Shares and/or the Common Shares, if any, which may become issuable pursuant to this Performance Share Award contrary to the provisions of this Award Agreement or the Plan shall be null and void and without force or effect.\nThe Participant shall be entitled to receive credits (“Dividend Equivalents”) based upon the cash dividends or cash distributions that would have been declared and paid with respect to the Performance Shares as if the equivalent number of Common Shares were held by the Participant. Dividend Equivalents shall be deemed to be reinvested in additional Common Shares (which may thereafter accrue additional Dividend Equivalents). Any such reinvestment shall be at the Fair Market Value of the Common Shares on the date of such reinvestment. The Participant shall also have the right to accrue Dividend Equivalents based upon the stock dividends or stock distributions that would have been declared and paid with respect to the Performance Shares as if the equivalent number of Common Shares were held by the Participant. With respect to any unvested Performance Shares, all Dividend Equivalents or distributions shall likewise vest in the same manner as the Performance Shares as to which such Dividend Equivalents or distributions relate. In the event any Performance Shares do not vest pursuant to Section 2 above, the Participant shall forfeit his or her right to any Dividend Equivalents accrued with respect to such unvested and forfeited Performance Shares.\nThe Performance Shares awarded pursuant to this Award Agreement do not and shall not entitle the Participant to any rights of a shareholder of the Company prior to the date Common Shares are issued to the Participant pursuant to Section 3 above.\nTo the extent that the Company is required to withhold Federal, state or other taxes in connection with the vesting of all or any portion of the Performance Shares and the issuance of an equivalent number of Common Shares, and the amounts available to the Company are insufficient for such withholding, it shall be a condition to the obligation of the Company to make any delivery Common Shares to the Participant that the Participant make arrangements satisfactory to the Company for payment of the balance of such taxes required to be withheld.\nAny notice required to be given pursuant to this Award Agreement or the Plan shall be in writing and shall be deemed to be delivered upon receipt or, in the case of notices by the Company,\nfive (5) days after deposit in the U.S. mail, postage prepaid, addressed to the Participant at the address last provided for his or her employee records.\nThis Award Agreement is made pursuant to the Plan and shall be interpreted to comply therewith. Any provision of this Award Agreement inconsistent with the Plan shall be considered void and replaced with the applicable provision of the Plan.\nThis Award Agreement, together with the Plan, embodies the entire agreement and understanding between the parties hereto with respect to the subject matter hereof and supersedes all prior oral or written agreements and understandings relating to the subject matter hereof. No statement, representation, warranty, covenant or agreement not expressly set forth in this Award Agreement shall affect or be used to interpret, change or restrict the express terms and provisions of this Award Agreement, provided, however, in any event, this Award Agreement shall be subject to and governed by the Plan.\nIn the event that one or more of the provisions of this Award Agreement shall be invalidated for any reason by a court of competent jurisdiction, any provision so invalidated shall be deemed to be separable from the other provisions hereof, and the remaining provisions hereof shall continue to be valid and fully enforceable.\nThe Company may, in its sole discretion, deliver any documents related to the Performance Shares and the Participant’s participation in the Plan, or future awards that may be granted under the Plan, by electronic means or request the Participant’s consent to participate in the Plan by electronic means. The Participant hereby consents to receive such documents by electronic delivery and, if requested, agrees to participate in the Plan through an on-line or electronic system established and maintained by the Company or another third party designated by the Company.\nThis Award Agreement may be executed in one or more counterparts, each of which shall be deemed to be an original but all of which together will constitute one and the same agreement."} | ||
| {"idx": 9, "order": 4, "level": 1, "span": "3. Issuance of Certificates"} | ||
| {"idx": 9, "order": 5, "level": 1, "span": "4. Restrictions on Transfer"} | ||
| {"idx": 9, "order": 6, "level": 1, "span": "5. Dividends and Other Distributions"} | ||
| {"idx": 9, "order": 7, "level": 1, "span": "6. No Shareholder Rights"} | ||
| {"idx": 9, "order": 8, "level": 1, "span": "7. Withholding"} | ||
| {"idx": 9, "order": 9, "level": 1, "span": "8. Notices"} | ||
| {"idx": 9, "order": 10, "level": 1, "span": "9. Award Agreement Subject to Plan"} | ||
| {"idx": 9, "order": 11, "level": 1, "span": "10. Entire Agreement"} | ||
| {"idx": 9, "order": 12, "level": 1, "span": "11. Severability"} | ||
| {"idx": 9, "order": 13, "level": 1, "span": "12. Electronic Delivery"} | ||
| {"idx": 9, "order": 14, "level": 1, "span": "13. Counterparts"} |
There was a problem hiding this comment.
Numbered sections (e.g., "1.No Right...", "2. Vesting...", and the subsequent headers for sections 3-13) are incorrectly assigned Level 1. According to the structural hierarchy defined in the rubric, top-level numbered sections should be Level 2.
| {"idx": 9, "order": 16, "level": 2, "span": "COMPANY\n:"} | ||
| {"idx": 9, "order": 17, "level": 2, "span": "CSW INDUSTRIALS, INC.\nBy: Joseph B. Armes"} | ||
| {"idx": 9, "order": 18, "level": 2, "span": "Chief Executive Officer"} | ||
| {"idx": 9, "order": 19, "level": 2, "span": "PARTICIPANT\n:"} |
There was a problem hiding this comment.
The signature block components (e.g., "COMPANY:", "PARTICIPANT:") are assigned Level 2. The rubric explicitly states that the signature block should be Level 1. This appears to be a regression or misclassification in the level logic for this document.
|
CodeAnt AI finished reviewing your PR. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
Triage agent — PR #82 comment review (read-only pass, no code changes) 3 inline comments reviewed (all from gemini-code-assist, all HIGH):
NEED-DISCUSSION (1 frozen-output decision, 3 aspects): idx=9 freeze validity — L0 split, numbered section levels, sig-block level. All three are interconnected; one re-freeze decision addresses all. Triage only — no code changes made this round. |
1 participant
User description
Summary
Tenth stacked PR. Adds idx=9 (Performance Share Award Agreement, CSW Industrials, Inc. Exhibit 10.9) as the tenth verified frozen baseline on top of idx=8 (PR #81).
No parser changes needed. The current parser handles idx=9 cleanly. This PR is freeze-only.
Verified output for idx=9
{L0:1, L1:15, L2:4}Top-level structure
Section 2 body absorption (acceptable per rubric)
doc2dict's HTML walker absorbed Sections 3-13's body prose into Section 2's body record (the HTML source chains paragraphs without per-section container divs). All 13 section HEADERS are emitted as separate L1 records in correct order — so structural hierarchy is intact even though body text is consolidated. The rubric (
level_rubric.md§"Common parser failure modes") explicitly accommodates this: the parser "preserves doc2dict's natural HTML grouping" rather than imposing its own splitting.Content is NOT lost — independent reconstruction measurement reports 99.5% word coverage (only 2 missing words: "31" and "st" from "31st" tokenization edge case).
Test plan
uv run scripts/parse_doc2dict_with_config.py --limit 10 --no-truncate --output-dir data/auto_parseexits 0 withok 10uv run scripts/level_loop/freeze.py 9 --forcereports word_coverage ≥ 90% (98.4%)uv run scripts/level_loop/regress.pyreports all 10 frozen idxs OKSource
http://www.sec.gov/Archives/edgar/data/1624794/000162479417000014/exhibit109performancesharea.htm
🤖 Generated with Claude Code
CodeAnt-AI Description
Add frozen baseline for idx=9 Performance Share Award Agreement
What Changed
Impact
✅ More coverage for contract parsing baselines✅ Stable reference output for future parser checks✅ Fewer false alarms when validating this agreement type🔄 Retrigger CodeAnt AI Review
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.