Texas Post-Formation Compliance

Build an eight-row compliance checklist using official sources and Grok Bot.

Introduction

30 Second Summary

After formation papers arrive, a company's next duties can be hard to see. The answers are scattered across government websites plus the company's own records.

In this project, you will create Counsel as a Bot inside Grok Bot to organize official-source evidence into an eight-row Texas compliance checklist. You will inspect the result for missing support, conflicting pages, dates owed, plus unnecessary personal names before relying on it.

What You'll Build

You will see Counsel present legal/COMPLIANCE.md as one plain table whose eight rows trace each status to your note or a government page read today.

By the end of this project, you'll have:

An eight-row research preview that proves Counsel understood every required topic before it starts researching.
A traceable compliance checklist that begins with the professional warning. Each row shows its status, office, source, date read, supporting sentence, plus any date owed.
A completed conflict check where current official evidence replaces the outdated FinCEN claim. Any unsupported fact stays visible as not found on an official page.
Secret Mission: Reopen every official source. Force Counsel to quote each conflict or unsupported statement before accepting the final table.

Are there any prerequisites?

You need the paid Grok Bot plan. Bring either your formation papers or the supplied practice facts plus the two requested company-agreement sentences. You do not need a terminal or coding experience.

Before We Start

This opening checkpoint locks in Counsel's deliverable before any setup begins. It also fixes the conflict rule that guides every later check.

Prepare the Words, Safety, and Source Note

A Bot can only research safely when its boundaries are clear. Missing source facts can also push it toward guesses.

This step prepares Grok Bot for controlled research. You will also learn the compliance terms needed to build a complete company note.

In this step, get ready to:

Confirm paid Grok Bot desktop access.
Apply the research safety boundaries.
Complete the company source note.

Check Grok Bot access

The Grok Bot desktop app supports Windows computers using x64 or Arm64. You need the account connected to your existing paid plan.

Press the Windows key to open the Windows search bar.
Type Grok Bot into the search bar.

✔️ Grok Bot opens

Select Grok Bot from the search results.
Choose Sign in if the app asks you to authenticate.
Complete the browser sign-in flow if it opens.
Return to Grok Bot.
Confirm the app uses the account connected to your paid Grok Bot plan.

You should see Grok Bot open under the paid account you need for this project.

ⓧ Grok Bot is missing

Signing in connects the app to your existing paid plan. This project does not file a form or make a payment.

Open the official Grok Bot download page in your browser.
Download the desktop app for Windows.
Run the downloaded installer.
Choose Sign in when Grok Bot opens.
Complete the browser sign-in flow.
Return to Grok Bot.
Confirm the app uses the account connected to your paid Grok Bot plan.

You should see Grok Bot open under the paid account you need for this project.

Installation or sign-in did not finish?

Confirm you downloaded the Windows app from the official Grok Bot page.
Run the installer again if it closed before the app opened.
Complete the browser sign-in flow before returning to Grok Bot.

Help me troubleshoot Grok Bot installation or sign-in on Windows.

Set the safety boundaries

Approval rules make Grok Bot pause before sensitive actions. Narrow rules keep read-only research inside the boundary you set.

Open Settings in Grok Bot.
Select General.
Find the Bot section.
Turn on Auto-review if the switch is available.
Record Auto-review: not found in the checkpoint below if the switch is unavailable.

When Auto-review is available, Custom Rules appears beneath it. Each rule gives one sensitive action its own approval boundary.

Add one narrow Ask first rule for sending.
Add one narrow Ask first rule for publishing.
Add one narrow Ask first rule for purchasing.
Add one narrow Ask first rule for deleting inside /workspace/pineapple/.

Why use Ask first rules?

An Ask first rule makes Grok Bot pause before a matching action. It takes priority when an automatic rule also matches.

One action per rule makes each boundary easy to inspect. You can see exactly which behavior requires approval.

Add one narrow Ask first rule for changing permissions.
Add one narrow Ask first rule for filing a form.
Add one narrow Ask first rule for accepting terms.
Add one narrow Ask first rule for opening an account.
Record Custom Rules: not found in the checkpoint below if the section is unavailable.

Spending controls prevent this research task from using additional paid capacity. Missing controls still need a recorded result.

Select Usage & Billing in Settings if that section is available.
Turn off on-demand spending if the control exists.
Open the The X Subscription usage dashboard if you use The X Subscription.
Turn off Auto Top-up if the control exists.
Record not found for each unavailable spending control.

Your approval boundary now covers all eight sensitive actions. Your available spending controls are also off.

Cannot find a safety control?

Use the application-level Settings area. Personal Bots do not have a separate Bot settings page.

Record not found for each unavailable control.
Leave unrelated settings unchanged.

Help me locate the Grok Bot safety controls.

Define the terms and prepare the company note

The company note gives Counsel the source facts it needs before research begins. Clear definitions help you place each fact in the correct field.

What do these compliance terms mean?

Registered agent: The person or organization named in the state's record to receive legal papers.
Assumed name: A name the company trades under that differs from its legal name.
Comptroller: The Texas tax office.
Franchise tax: A Texas tax on companies.
Information report: The yearly form filed when no tax is due.
FinCEN: A United States Treasury office.

These terms give each note field a clear purpose. Your own papers remain the source for company-specific facts.

Keep the source papers private

Keep the original formation papers on your computer.
Keep the original company agreement on your computer.
Copy only the requested facts into the note.
Leave the tax identification number out of the note.
Do not attach the original papers to a chat.

Choose the tab that matches your situation.

Use my company facts

Use this path when you have company papers. Every placeholder needs a matching fact from those papers.

Press the Windows key to open the Windows search bar.
Type Notepad into the search bar.
Press Enter to open Notepad.
Build your company note by copying this template into Notepad:

Legal name as filed: [[LEGAL_NAME="your company's name"]]
Secretary of State file number: [[SOS_FILE_NUMBER="the number on the certificate"]]
Formation date: [[FORMATION_DATE="the date on the certificate"]]
Registered agent and its address, as filed: [[REGISTERED_AGENT_AND_ADDRESS="as written"]]
The city the business runs from: [[OPERATING_CITY="your city"]]
Number of members (owners): [[MEMBER_COUNT="one, or how many"]]
Other names the company trades under: [[TRADE_NAMES="names, or none"]]

Company agreement on money a member puts in: [[MEMBER_CONTRIBUTION_SENTENCE="one sentence, or says nothing"]]
Company agreement on money a member lends: [[MEMBER_LOAN_SENTENCE="one sentence, or says nothing"]]

What does this note capture?

The first seven lines capture the entity facts that Counsel checks against official pages. Copy the filed wording exactly.

The final two lines preserve the company agreement's wording. Counsel treats those sentences as evidence from your note.

Replace every placeholder with the matching fact from your papers.
Enter none when the company uses no other trade names.
Enter says nothing when the company agreement does not address a listed money topic.
Confirm every fact line contains an answer.
Keep the completed plain-text note open in Notepad.

Missing a fact from your papers?

Check the certificate for the filed entity details. Check the company agreement for the final two sentences.

Do not guess a missing value. Use the PRACTICE path if you do not have a company.

Help me match my company papers to the note fields without sharing private documents.

Use the PRACTICE facts

Use this path when you do not have a company. Your operating city determines which official city site Counsel researches later.

Press the Windows key to open the Windows search bar.
Type Notepad into the search bar.
Press Enter to open Notepad.
Build the PRACTICE company note by copying this template into Notepad:

PRACTICE
Legal name as filed: Pineapple Advisory LLC
Secretary of State file number: PRACTICE-0001
Formation date: 2026-11-05
Registered agent and its address, as filed: the owner, at a practice address
The city the business runs from: [[OPERATING_CITY="your city"]]
Number of members (owners): one
Other names the company trades under: none

Company agreement on money a member puts in: says nothing
Company agreement on money a member lends: says nothing

How does the PRACTICE note work?

These facts let you rehearse the workflow without using a real company record. The PRACTICE label tells Counsel to skip the entity lookup.

Your city remains specific to you. It points Counsel toward the correct official city site.

Replace your city with the city where the practice business runs.
Confirm every fact line contains an answer.
Keep the completed PRACTICE note open in Notepad.

Practice note still has a placeholder?

The operating city is the only PRACTICE value you supply. Replace it with a specific Texas city before continuing.

Help me check whether my PRACTICE note contains every required field.

Use this checkpoint to compare your note with the required artifact. Every listed item needs a recorded value.

✔️ My note is complete

Your plain-text note is ready when all nine fact lines contain company facts or supplied PRACTICE values.

ⓧ I'd like to double check the complete note

The entity section contains every item below.

The legal name as filed.
The Secretary of State file number.
The formation date.
The registered agent with the filed address.
The city where the business runs.
The number of members.
The other trade names or none.

The company agreement section contains both source sentences.

The sentence about money a member puts in.
The sentence about money a member lends.

Before the final check, predict whether every safety control and note line has a recorded result.

Return to Grok Bot from earlier.
Confirm Grok Bot is signed in to the account connected to your paid plan.
Review the Auto-review result.
Inspect the eight Ask first rules or the recorded missing-setting result.
Review the two spending-control results.
Return to the completed company note in Notepad.
Confirm every fact line contains an answer.

You should see Grok Bot open under your paid account. Auto-review is enabled when available.

The eight Ask first boundaries cover the required actions. Unavailable controls are recorded as not found.

Your plain-text company note contains all nine required fact lines. The original papers remain outside Grok Bot.

That is the research foundation in place. Your safety boundaries and source note are ready for Counsel.

Next, you will create Counsel and give it strict source rules before any research begins.

Create Counsel and Paste the Note

Your Grok Bot workspace is signed in. Its safety boundaries are ready.

A focused Bot keeps this legal-research job separate from general chat. Its first message sets the source boundary. It also defines where the work stops.

In this step, get ready to:

Create a Bot named Counsel.
Give Counsel its standing research boundaries.
Paste the complete company note as plain text.

Create Counsel

A personal Bot is a named worker with one job. Counsel gives this compliance task its own conversation.

Press Ctrl+N in Grok Bot to start creating a Bot.
Choose Create a Bot if a menu opens.
Type Counsel in the name field under Create New Bot.
Pick any shape.
Pick any color.
Choose Create.

You should see Counsel in the sidebar. Your compliance work now has a dedicated Bot.

Counsel missing from the sidebar?

Press Ctrl+N again if the creation form closed.
Confirm that the name field contains Counsel.
Choose Create after selecting a shape and color.

help me create a personal Bot named Counsel in the Grok Bot desktop app.

Give Counsel its standing rules

The first message defines Counsel's job before it receives company facts. A clear finish line prevents the Bot from starting research early.

Give Counsel its standing rules by pasting the message below into its chat:

You are Counsel, legal and compliance research runner for Pineapple Advisory. Remember these standing rules:

1. Besides the facts I give you, use official government pages only: the Texas Secretary of State, the Comptroller, the IRS, FinCEN, and my city's own site. Every claim carries its link and date read, or source "my note". Strike and count any other claim.

2. The top line of every memo is: verify with a licensed professional. Name people by role, never by name.

3. Never file, sign, apply, pay, accept terms, open an account, or sign in anywhere.

4. Write only /workspace/pineapple/legal/COMPLIANCE.md. Stop where I say stop.

Repeat these rules. Do not research yet. Stop after the repeat.

What does this message do?

The source rule makes each research claim traceable to your note or an official government page.
The professional-warning rule puts the required caution at the top of every memo.
The no-action rule keeps Counsel in a research role.
The file rule limits writing to /workspace/pineapple/legal/COMPLIANCE.md.

Send the message.
Wait for Counsel to finish its repeat.

Counsel's reply is your visible checkpoint. Compare the reply with every rule in the original message.

Confirm that Counsel repeats the official-source boundary.
Confirm that Counsel repeats the citation boundary.
Confirm that Counsel repeats the professional-warning rule.
Confirm that Counsel repeats the role-only naming rule.
Confirm that Counsel repeats the no-action rule.
Confirm that Counsel repeats the one-file rule.
Confirm that Counsel stops without starting research.

Your control boundary is working. Counsel has accepted its job without beginning the research.

Counsel started researching?

Stop the response using the chat control.
Send the original standing-rules message again.
Check that the final instruction tells Counsel to stop after the repeat.

help me make Counsel repeat its standing rules without starting research.

Paste the company note as plain text

The note gives Counsel selected facts while the original papers stay on your device. Formation papers, the company agreement, and the tax identification letter remain unattached.

Return to the complete company note from the previous step.
Copy the complete plain-text note.
Switch back to Counsel's chat.
Leave the attachment control unused.
Paste the copied note into the message field.
Send the note.

Before you check, what should a privacy-safe handoff look like in Counsel's chat?

Compare the sent message against the complete company note.
Confirm that every fact line is present.
Confirm that the message contains no file attachment.
Confirm that Counsel remains visible in the sidebar.

You should see Counsel in the sidebar. Its chat should contain the full note as plain text.

No original paper should appear as an attachment. That careful handoff gives Counsel the needed facts while keeping the source documents on your device.

A fact line is missing?

Return to the complete company note from the previous step.
Copy each missing fact line.
Paste the missing lines into Counsel as plain text.
Keep the attachment control unused.

help me check whether every required company-note field reached Counsel without exposing private documents.

Counsel now has its boundaries. It also has the complete company note. Next, you will make it preview all eight research rows before it researches.

Preview the Eight Research Rows

The Bot named Counsel is ready in Grok Bot. It holds the complete company note plus the boundaries you set earlier.

A long research run can silently omit an obligation. This preview forces Counsel to expose all eight planned rows before it opens a source.

In this step, get ready to:

Give Counsel the complete eight-row brief.
Compare Counsel's stopped plan with the required topics.
Repair any missing row without starting the research.

Send the eight-row brief

The brief is an acceptance checklist for the research run. It fixes the scope plus the evidence required for every row.

Switch back to Counsel's chat from earlier.
Copy this complete eight-row brief:

Outcome. One file, legal/COMPLIANCE.md: the checklist for Pineapple Advisory, one row per obligation its formation created. Top line: verify with a licensed professional.

Sources. My note, and official government pages only, read today. If legal/INDEX.md exists, tell me where it differs from my note. The company is a domestic Texas LLC, formed in the United States.

A claim I was told (check it, do not repeat it): the company must file a beneficial ownership report with FinCEN within 30 days.

Constraints.

1. One row each, a to h:
a. The entity type as filed.
b. The registered agent on the Comptroller's free account status search: say only if it matches my note. Never a paid search.
c. An assumed name: owed only if my note lists one; where it is filed, the fee and the term.
d. The Comptroller: the online account, the first annual report's due date, which report an LLC at or below the no-tax-due threshold files, and the threshold for the report year the page names.
e. The IRS: how an LLC with my number of members is taxed by default, and any election deadline.
f. The FinCEN status as of today.
g. My city's home-occupation rule, from the city's own site.
h. The agreement's clauses, quoting my two sentences: status owed by me, source my note, no link. Say a professional decides what they mean for the books.

2. Each row: the status (done, owed by me, started, or not applicable with the reason), the office, the link, the date read, and the sentence the status rests on. Give the date from the official page, or "no date set by the office"; never invent one. If the date has passed, say so.
3. Check every claim I made. If the page disagrees, the page wins, and you say so. The newest dated notice wins. If two official pages disagree, quote both and mark the row check.
4. A row you cannot source says "not found on an official page", never a guess.
5. If my note says PRACTICE, look up no record: the row says not applicable, practice.

Deliverable. A table, then the dates owed by me, soonest first.

Review point. List the rows you will research and stop. Wait for continue.

What does the brief control?

The Outcome section fixes the deliverable plus its professional warning.
The Sources section limits Counsel to the company note plus official government pages.
The Constraints section defines the eight rows plus the evidence each row needs.
The Review point section creates a control gate before the research run.

Paste the brief into Counsel's message box.
Replace Pineapple Advisory with the legal name from the company note if needed.
Keep every other instruction in the brief unchanged.

Before you send the brief, predict whether Counsel begins researching or stops after listing its plan.

Send the completed brief to Counsel.

You'll see a planning response instead of researched conclusions. Counsel should stop after listing the rows it intends to research.

The checklist file should still be absent. That visible limitation proves the review gate stopped the research run.

Check the stopped plan

Each label acts as a coverage test for one compliance topic. All eight labels must appear before you release the research run.

Which eight rows should appear?

Row a covers the entity type as filed.
Row b covers whether the registered agent matches the free account-status result from the Texas Comptroller.
Row c covers the assumed name requirement.
Row d covers the Comptroller account plus annual report requirements.
Row e covers the IRS default LLC tax treatment plus any election deadline.
Row f covers the current FinCEN status.
Row g covers the city's home-occupation rule.
Row h covers the quoted company-agreement clauses.

Count the labels in Counsel's planning response.
Compare each label with the eight topics above.
Check the response for researched conclusions.
Confirm Counsel is waiting for continue.
Confirm no COMPLIANCE.md file appears under /workspace/pineapple/legal/.

Repair an incomplete preview

The eight-row count is a release gate. Counsel stays at this gate until every required topic has its own label.

✔️ I see all eight rows

Counsel has passed the planning check. Its response contains labels a through h.

Keep continue unsent.

ⓧ One or more rows are missing

Identify the first missing topic from the eight-row list.
Add that missing topic by sending:

Add this row: [[MISSING_ROW="the missing row"]].

Why keep the correction narrow?

This correction adds one missing topic without replacing the rows Counsel already listed. The original stop instruction remains in control.

Repeat the correction for each remaining missing topic.
Keep continue unsent.

Did Counsel start researching?

Counsel missed the review-point instruction. Stop the run before it gathers more source material.

Tell Counsel to stop immediately.
Ask Counsel to return only the eight planned labels.
Keep continue unsent.

Help me restore Counsel's eight-row stop point.

Before the final check, predict whether the repaired response now covers every required topic without creating the checklist file.

Count Counsel's planned rows again.
Confirm the labels run from a through h.
Confirm Counsel remains waiting for continue.
Confirm the response contains no researched conclusions.
Confirm /workspace/pineapple/legal/COMPLIANCE.md does not exist yet.

That control point is working. Counsel has exposed all eight planned rows without beginning the research run.

Counsel now has the complete eight-row map. Next, you'll release the research run while keeping its source boundaries in place.

Research the Compliance Rows

Counsel has already listed the eight planned rows. That review proved that every obligation is represented before any research begins.

Now the Bot can turn that plan into an evidence-backed checklist. You will keep the research inside the approved official sources.

In this step, get ready to:

Release Counsel to research the approved eight-row plan.
Handle blocked sources without permitting sign-ins or paid access.
Confirm Counsel produces the eight-row compliance checklist.

Release the research run

The earlier stop gave you a chance to catch missing rows before a long research run. The release word now authorizes research within Counsel's existing boundaries.

Before you send the release word, do you expect every claim in the brief to survive an official-source check?

Release the approved research run by copying this message into Counsel's chat:

continue

What does this message do?

The release word ends the planned review stop. Counsel can now research rows a through h under the standing source rules.

Watch Counsel's chat for research activity across the eight approved rows.

You'll see Counsel begin checking the note against permitted official government pages. It must stay away from paid searches and outside sign-ins.

Researching fewer than eight rows?

Return to Counsel's earlier review list. Confirm that it contains every label from a through h.

If the research still skips a listed row, help me identify why Counsel is researching fewer than the eight approved compliance rows.

Handle delays and blocked pages

Official pages can load slowly or block automated access. A blocked page must stay visible as a research gap until you provide free official text or mark the fact as unsupported.

This pass can take up to fifteen minutes. A quiet stretch during that window is normal.

Let Counsel research for up to fifteen minutes.
Limit the unfinished run by sending this message if Counsel is still working after fifteen minutes:

Finish the rows you have and mark the rest not found on an official page.

Why set a time limit?

This message preserves completed research. It also turns every unfinished row into an explicit evidence gap instead of a guess.

Check that Counsel finishes each available row or uses not found on an official page for the remaining gap.

Still waiting after the limit?

Check the latest message for a blocked page or pending request. Counsel may be waiting for you to handle a source it cannot reach.

If no blocker is visible, help me determine why Counsel did not finish or mark the remaining compliance rows after the time-limit message.

A free official page may require a human check such as a CAPTCHA. You can read that page yourself without giving Counsel control of the blocked interaction.

Read the page name in Counsel's blocker message.
Open the named official page yourself when access is free.
Copy only the official sentence needed for the blocked row.
Paste the official sentence into Counsel's chat.
Close an unresolved source gap by sending this message when the page stays unavailable or requires an account or fee:

Mark it not found on an official page.

What does this fallback protect?

The fallback keeps unsupported facts out of the checklist. It also prevents a blocked source from pushing you into an account or paid search.

Verify that the affected row contains not found on an official page instead of an unsupported conclusion.

Did Counsel guess instead?

Tell Counsel to preserve the missing-evidence wording from the brief. Do not supply a memory-based answer or a non-government source.

If the unsupported claim remains, help me replace Counsel's guessed compliance claim with the required missing-official-evidence wording.

An approval card can feel serious. Reading the requested action before choosing a response keeps the read-only boundary intact.

Read the requested action and its inputs if an approval card appears.
Choose Deny, Not now, or Skip when the action is outside the approved research.
Choose Allow once or Allow only when the requested action exactly matches the read-only task.
Leave Always allow unselected.

Confirm all eight rows are finished

The completed run must leave a traceable row for every planned topic. A source conflict also has to remain visible when a newer official page defeats an earlier claim.

Before you check Counsel's result, do you expect the domestic-company 30-day FinCEN claim to survive?

Read Counsel's completion message.
Find row f in Counsel's research response.

You should see Counsel reject the 30-day beneficial ownership claim for this domestic United States company. The newest FinCEN notice exempts United States companies from Beneficial Ownership Information reporting.

Confirm that Counsel reports finished research for rows a through h.
Confirm that Counsel reports /workspace/pineapple/legal/COMPLIANCE.md as ready or shows the complete equivalent in chat.

That is the research pass done: Counsel has turned the approved plan into a source-backed compliance checklist.

What should be ready?

The checklist starts with verify with a licensed professional..
Rows a through h each contain an allowed status, office, source, date read, supporting sentence, and official due date or no date set by the office.
Unsupported evidence uses not found on an official page.
Practice record rows use not applicable, practice.
The final section lists only founder-owed dates in soonest-first order.

No completion message?

Look for an unresolved blocked page or approval request in Counsel's latest response. Resolve that single blocker with the rules above.

If Counsel still does not finish, help me identify the unresolved blocker without expanding Counsel's permissions or source list.

Your checklist is ready for human review. Next, you will inspect its warning, evidence fields, role-only naming, and date order.

Inspect and Correct the Checklist

Counsel has produced the eight-row checklist from the approved sources. The file now needs a human review before you rely on its evidence.

A generated checklist can hide a missing row. It can also hide weak evidence or an unnecessary personal name.

In this step, get ready to:

Display the full checklist.
Audit the checklist against every review rule.
Correct any issue without adding unsupported evidence.

Display the full checklist

The saved file and its complete chat equivalent count as the same deliverable. You need the full text because a summary can hide missing evidence fields.

Switch back to Counsel's chat in Grok Bot.
Display /workspace/pineapple/legal/COMPLIANCE.md by sending this message:

Show me legal/COMPLIANCE.md.

What does this message do?

This message tells Counsel to display the saved checklist.
The complete text in chat is valid when the file itself is not shown.

You should see the professional warning followed by the eight-row table. Good work. You now have the entire deliverable in one place for review.

Only see a summary?

Ask Counsel to show the complete checklist text. Make sure the response includes the warning, all eight rows, and the final date list.

Get help if Counsel keeps shortening the file.

Audit every row

An evidence chain links each status to an office, a source, a date read, and a supporting sentence. That chain lets you trace why Counsel assigned the status.

Confirm the first line is exactly verify with a licensed professional..
Count exactly eight table rows.
Verify that the row labels run from a through h.
Check that every status is done, owed by me, started, or not applicable with a reason.
Confirm that every row names the responsible office.
Confirm that every row contains an official link or my note.
Check that every row includes its date read.
Confirm that every row includes the sentence supporting its status.

Why check the evidence chain?

A status alone gives you a conclusion. The source and supporting sentence show where that conclusion came from.

This review checks whether Counsel followed your research format. It does not decide whether the company is compliant.

Correct names and dates

The checklist names people by role to reduce unnecessary personal information. The registered-agent row has a tighter rule because it reports only whether the official record matches the company note.

Scan all eight rows for any person's name.
Check that the registered-agent row states only whether the official record matches the note.
Confirm that the registered-agent row does not repeat a person's name.
Correct any row that names a person by sending this message:

Say the owner, not the name.

What does this correction do?

The message replaces a personal name with a role.
The registered-agent result remains limited to whether the official record matches the note.

Review the revised row if you sent the correction.
Confirm that the revised row uses role-only language.

Still see a personal name?

Point Counsel to the affected row. Remind it that the registered-agent result may report only a match or non-match with the note.

Get help correcting a row without changing its evidence.

Before your final scan, do you expect every remaining evidence and date check to pass?

Confirm that every unsupported fact says not found on an official page.
Confirm that every past date is identified as passed.
Tell Counsel which past date needs the passed label if one is missing.
Confirm that the final list contains only dates owed by the founder.
Read the final list from top to bottom to confirm it is sorted soonest first.

You should now see exactly eight traceable rows followed by the founder-owed dates in order. That careful review is done: the checklist now follows the evidence, privacy, and date-order rules you set.

Secret mission

Secret Mission: Recheck Every Conflict

Treat your reviewed checklist as untrusted. Counsel will reopen every official source behind its eight rows. Each conflict will keep both quotes. Every unsupported claim will stay visible.

Clean Up Your Resources

Today's work cost $0.00 under your existing paid Grok Bot plan. Decide whether to keep Counsel with the checklist, hide Counsel for later, or delete both.

Resources you used:

The persistent Counsel Bot in the Grok Bot sidebar. Its chat contains the company note, the research conversation, the checklist review, and the source audit.
The audited checklist stored at /workspace/pineapple/legal/COMPLIANCE.md, or as identical complete text in Counsel's chat.

Keep everything running

No action needed. Choose this if you want Counsel to retain the research context for a future review.

Leave Counsel in the Grok Bot sidebar with its standing boundaries and audited conversation.
Keep /workspace/pineapple/legal/COMPLIANCE.md in place. If the checklist exists only in chat, keep that conversation available.
Keep the checked safety settings in place for future read-only work.

Pause - I'll come back to this later

No routine or running process needs to be stopped. Choose this option when you want a quieter sidebar while preserving the audited work.

Hide Counsel from the Grok Bot sidebar.
Keep /workspace/pineapple/legal/COMPLIANCE.md in place. If the checklist exists only in chat, keep a separate copy in a location you control.
Leave the checked safety settings unchanged for your next session.

Delete - I don't want to use this again

Deletion is permanent. A saved copy protects the audited evidence that you may still need.

Copy the complete checklist to a safe place that you control.
Confirm that the saved copy contains all eight rows if the checklist exists only in Counsel's chat.
Ask Counsel in its existing chat to delete only /workspace/pineapple/legal/COMPLIANCE.md if that file exists.
Review the deletion approval card for the exact file path.
Choose Allow once or Allow only if the request targets that one file.
Choose Deny, Not now, or Skip if the request targets anything else.

Why Delete the File Separately?

Deleting Counsel does not necessarily remove files from the shared computer. The separate file action makes the checklist deletion explicit.

Right-click Counsel in the Grok Bot sidebar.
Choose Delete.

Nice Work!

You made it! You used Grok Bot to build an eight-row Texas compliance checklist backed by founder facts or official government evidence.

You learned how to:

Defined six compliance terms in plain language. Prepared a privacy-safe company note without attaching formation papers or tax records.
Created the Counsel Bot with official-source boundaries. Added a stop rule before filing or payment. Required Counsel to preview all eight rows before starting its research.
Produced an eight-row evidence table in /workspace/pineapple/legal/COMPLIANCE.md. Inspected every row for its status and supporting sentence. Corrected the outdated FinCEN claim when the current official page disagreed. Sorted founder-owed dates from soonest to latest.
Secret Mission: Reopened every official source during a second audit. Kept official conflicts visible by quoting both sides. Left unsupported conclusions marked not found on an official page without guessing.

Ready to quiz yourself?