Take a look

 Kishan

 

Study following

 

With regards,

 

Hemen Parekh 

 

Hey Bro : Here is my query to Kishan and his answer. Would you like to provide some sharp instructions to Kishan on how to implement this ? > [7:47 am, 28/09/2026] Hemen Parekh: I await your confirmation that there will be automatically posting on Facebook and X also

Talking of postings on different Social media, more and more Celebrity are posting their views on these - especially on X

Could you get our Search Agent to scan such posting and write a blog - or, my own short post - on that very same media as a kind of rejoinder?
[7:56 am, 28/09/2026] Hemen Parekh: This " extension " of the capabilities of our Agent will justify renaming it " Content Genie 3 "

Who knows, 6 months down the line, Content Genie might be even able to generate videos in response to already posted videos on Education, AI , Government etc

A truly multi media Content Creator as , you have already done to some extent on Your Content Creator

Incidentally, at the bottom of each and every posting, display:

Regards

Hemen Parekh

[Www.yourcontentcreator.in](https://Www.yourcontentcreator.in) // [8:02 am, 28/09/2026] Kishan Kokal: Can not think of anything else at the moment

I suppose we can see the real title of the blogs and clicking view will open a pop up so that i do not need to exit dashboard
Yes, you do not need to exit the dashboard
[8:04 am, 28/09/2026] Kishan Kokal: I await your confirmation that there will be automatically posting on Facebook and X also

Talking of postings on different Social media, more and more Celebrity are posting their views on these - especially on X

Could you get our Search Agent to scan such posting and write a blog - or, my own short post - on that very same media as a kind of rejoinder?
Yeah, we’ll post on linkedin, facebook and X

Talking about getting our Search Agent to scan X postings. That’s certainly doable.
[8:04 am, 28/09/2026] Kishan Kokal: This " extension " of the capabilities of our Agent will justify renaming it " Content Genie 3 "

Who knows, 6 months down the line, Content Genie might be even able to generate videos in response to already posted videos on Education, AI , Government etc

A truly multi media Content Creator as , you have already done to some extent on Your Content Creator

Incidentally, at the bottom of each and every posting, display:

Regards

Hemen Parekh

[Www.yourcontentcreator.in](https://Www.yourcontentcreator.in)
Noted

 

 

 

Bro, Kishan's "doable" is true, but a few of these features have platform rules he needs to know about now, or he'll build something that gets your accounts suspended. Here are instructions you can forward to him.

---

Instructions for Kishan: Content Genie 3 (X, Facebook, footer, rejoinders)

1. Facebook: post to a Page, not a personal profile

• Meta's Graph API allows automated posting to Facebook Pages, not to personal timelines. Please verify this against current Meta docs.
• Create a "Hemen Parekh" Page, get Page access via a Meta developer app, and post there.
• If Hemen wants his personal profile, generate the post and put it in a READY TO PUBLISH queue for one-click manual posting. Don't automate the browser.

2. X: use the official API only

• Use OAuth 2.0 with the create-post endpoint. Store the returned post ID for the audit log.
• Check the current API tier and pricing before promising anything. Reading and searching posts is typically the paid part.
• Do not scrape X. It violates their terms and will break.
• The X adapter should build a 280-character version, or a thread, from the master article. Never truncate the blog text.

3. The "scan celebrity posts → rejoinder" feature (add as a new module)

• Build a SocialListeningAgent. It watches a curated list of accounts and keywords, not all of X.
• Keep a Watchlist table (handle, topic tags, priority) that Hemen edits.
• Run it through the same pipeline as news: the post is treated as a "source", matched against Hemen's 6,800 blogs, scored, and researched.
• Reuse the existing stages (ForesightAgent, EvidencePack, FactCheck, Editorial) unchanged. Only the input type is new.
• Output can be a blog, a short X post, or both.

4. Guardrails specific to rejoinders (non-negotiable)

• No auto-replies or auto-mentions to celebrities. X's automation rules restrict unsolicited automated replies, and it's the fastest way to get the account flagged. Default to a standalone post or quote-post, with a link to the original.
• Human approval is mandatory for any output that names a real person. This overrides Trusted or Full Autonomous mode. The Safety Gate should hard-route these to Hemen.
• Quote the celebrity's post accurately, using the official embed or link rather than retyping it. Never paraphrase in a way that changes meaning, and never attribute anything the person didn't say.
• The rejoinder must argue with the idea, never the person. Add a rule in the EditorialAgent to reject anything that reads as a personal attack.
• Rate-limit it, for example a maximum of 2 rejoinders per day, so the account doesn't look like a bot.
• Label AI-assisted content where the platforms require or encourage it.

5. The footer: enforce it in code, not in the prompt

• Append this block deterministically in each platform adapter, after generation:

  Regards

  Hemen Parekh

  www.yourcontentcreator.in

• If the LLM writes the footer, it will eventually drop or garble it.
• Add a unit test that fails if any published payload lacks the footer.
• On X, the footer counts toward the character limit. Reserve space for it before generating.

6. Rename to "Content Genie 3" safely

• Make the product name a config value. Don't rename code, tables or repos.
• Rename only the UI, the dashboard and the published branding.

7. Video: park it, but design for it now

• Add a MediaAdapter interface (image today, video later) so video slots in without re-architecture.
• Video needs its own approval step, cost cap and quality check. Don't start it until text and social posting have run reliably for a few weeks.

8. Learning hook (ties back to our earlier discussion)

• Log every rejoinder that Hemen approves, edits or rejects, and treat it as a preference pair. This is the training data for the GEPA/DSPy loop I described.
• Track outcomes per platform separately. What works on X will not work on LinkedIn.

9. Suggested order

1. Facebook Page and X posting adapters, with the footer and audit log.
2. Watchlist and SocialListeningAgent, with the approval gate on.
3. Rejoinder generation.
4. Video, later.

---

Kishan should also confirm the X API cost and the Facebook profile-versus-Page limitation before the next demo, because both can change what you tell people is possible.

Re: Blog Genie 3

 I like the " Thought leadership " style

I would like feature to select the number of blogs. I plan to start with 2 blogs per day and if satisfied,  gradually increase to 10 per day

Publishing should be after 30 minutes interval

Hcp 

Get Outlook for Android

---

From: Kishan Kokal <kokalkishan.official@gmail.com>
Sent: Sunday, 27 September 2026 08:14:23
To: Hemen Parekh <hcp@recruitguru.com>
Subject: Blog Genie 3

 

A few questions regarding Blog Genie:

1. How many blogs should Blog Genie generate and publish per day? For example, 5, 10, 15, etc.?

2. How should the blogs be scheduled for publishing?
   For example, if we generate 5 blogs in the morning when the agent is automatically invoked at 9 AM, we could either:

   • Schedule them to be published at intervals of 1-2 hours throughout the day, or

   • Publish all 5 blogs at once.

   Let me know which approach you think would work better, or if you have another approach in mind.

3. Regarding the template: Since you're okay with the current template, we can stick with it. However, I've attached two templates I found in an open-source project. Feel free to take a look and let me know what you think. We'd obviously need to tweak them to fit our specific use case.
   
   

Warm regards,
Kishan

Blog Genie 3

 Kishan

In Blog Genie 2 , blog does occassionally mention that, in the past , I have written something about this topic. But it never shows any clickable link of any of my blogs 

As against this , in SearchMyBlogs tool , there are several clickable links of my earlier blogs , both inside the text of the blog and at the bottom, in the form of a tabulation. This is " overdoing " !

In Blog Genie 3 , I suggest a " moderate" method where :

:. Bottom table is eliminated altogether

:. Within the text , there are a couple of relevant blog links with brief description of what I had said in each of those blogs

Invariably, blog must reproduce clickable link of the relevant news item and a few lines telling about what that news is all about. That " Context " must appear right in the beginning and then link up with my " prior art " blogs

Of course, sole purpose is NOT to just establish " I had said this earlier "

There must be one or two paras of NEW suggestion s  about that topic, in light of changed circumstances

H

Re: Demo call | Hirism x 3P Consultants

 What is the status of Kishan 's Brihas

Get Outlook for Android

---

From: Prashant Sharma <prashant@3pconsultants.co.in>
Sent: Monday, 21 September 2026 16:22:31
To: Hemen Parekh <hcp@recruitguru.com>
Cc: Mitchelle Shetty <mitchelle@3pconsultants.co.in>; Mahendra Tarkhad <mahendra@3pconsultants.co.in>; Kishan Kokal <kokalkishan.official@gmail.com>
Subject: RE: Demo call | Hirism x 3P Consultants

 

Dear Sir,

Mahendra Kishan and I attended a demonstration of Hirism, and I would like to share our key observations and assessment below:

• Product maturity: Hirism is currently a relatively basic AI-enabled product and appears to be in the early stages of development, particularly for the recruitment industry.
• Core offering: The platform combines AI-based candidate parsing, CRM functionality, assignment management, and dashboard capabilities. It provides visibility into the workload of a larger contingent workforce, assignment progress, and the sales pipeline.
• Target user base: Based on the demonstration, the platform appears to be primarily designed for smaller recruitment firms that are still managing assignments through Excel sheets, folders, and basic cloud/local storage systems.
• Functional maturity: A significant number of features and functionalities are still under development, and the overall platform currently appears to have limited depth compared with more established recruitment-specific CRM solutions.
• Fitment for 3P: We explained our business model, the nature and complexity of our assignments, and the volume of mandates handled by our team. Based on this discussion, the Hirism team themselves agreed that the current platform is not ideally suited to our requirements.
• Comparison with Ezekia: From what we observed during the demo, Ezekia is considerably more advanced and comprehensive in terms of functionality, workflow management, and suitability for our executive search operations.

Overall, our assessment is that Hirism, in its current stage of development, does not offer a compelling alternative for our requirements. It may be more relevant for smaller recruitment firms that are looking to move away from basic Excel- and folder-based assignment management.

Regards,
Prashant

 

 

From: Mohd Raza <mohd.raza@hirism.com>
Sent: Tuesday, September 8, 2026 1:02 PM
To: Mitchelle Shetty <mitchelle@3pconsultants.co.in>
Cc: Kishan Kokal <kokalkishan.official@gmail.com>; Prashant Sharma <prashant@3pconsultants.co.in>; Manish Chauhan <accounts@3pconsultants.co.in>
Subject: Re: Demo call | Hirism x 3P Consultants

 

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Mitchelle,

I have already added the colleagues you copied on this thread : Kishan Kokal, Prashant Sharma, and Manish Chauhan to the demo invite for tomorrow, September 9th.

If there are any other names and email addresses you'd like to include, please share them and I'll be happy to add them to the calendar invite right away.

Best,

 

On Tue, 8 Sept 2026 at 09:18, Mitchelle Shetty <mitchelle@3pconsultants.co.in> wrote:

Can you please add the following team members to the demo.

 

Warm Regards,

 

Mitchelle Shetty

+919867550810

3P Consultants

 

Book time to meet with me

 

-----Original Appointment-----
From: Mohd Raza <mohd.raza@hirism.com>
Sent: 20 August 2026 17:46
To: Mohd Raza; Mitchelle Shetty; Sudip Bhattacharjee; Prashant Kumar; Mayank Diwaker; kokalkishan.official@gmail.com; Nikita; Prashant Sharma
Subject: Demo call | Hirism x 3P Consultants
When: 09 September 2026 15:00-16:00 Asia/Kolkata.
Where: https://meet.google.com/zsm-aeua-ixf

 

Some people who received this message don't often get email from mohd.raza@hirism.com. Learn why this is important

Congratulations

 Priyansh ,

 

Just came across this article in today’s Business Line :

“ The iron-air storage solution for solar ‘

Congratulations

I have been advocating use of GRID size Iron Air batteries since 2021 , as you will notice from :

Iron Air Battery to Store Solar Power

https://myblogepage.blogspot.com/2026/08/iron-air-battery-to-store-solar-power.html

With regards,

Hemen Parekh

www.Iam-Immortal.ai / www.HemenParekh.ai / www.IndiaAGI.ai

Very Timely Advice by CLAUDE for Blog Genie 3

 Kishan ,

 

Pl consider this if Clude’s reasoning is valid

 

Incidentally , for automatic posting, you mentioned > Blogger site / Personal.ai /  Linkedin

 

Pl also add >  Facebook and X

 

Hcp

 

 

Blog Genie 3.0 — Addendum A: Pre-Publish Safety Scan

Sep 19, 2026 · @Hemen Parekh

Purpose and scope

Blog Genie 3.0 must never publish text that contains a credential, private personal data or third-party correspondence. This addendum adds the scan that enforces that rule. The scan runs twice: once when an archive post is ingested, and again before every publish.

It applies to every target platform (Blogger, LinkedIn, X, Facebook, Personal.ai) and to every autonomy mode. Factual checks and prior-art matching stay in the existing verify stage; this layer sits beside them and does not replace them.

What the scan must catch

The archive holds private correspondence that was later posted publicly, and an agent mining 6,800+ posts will meet it. A 2013 post on the Emails (Others) blog is the worked example: it reproduces a full email chain that includes a login and plaintext password for an ad-network publisher account, several named third parties with their email addresses, and the terms of a revenue-share negotiation.

Four risks follow from that:

• Credentials: passwords, API keys, tokens, login pairs.
• Third-party personal data: email addresses, phone numbers, postal addresses, ID numbers.
• Third-party correspondence and terms: quoted emails, revenue splits and negotiating positions the other party never agreed to publish.
• Unpublished or confidential material: drafts, unsent letters, internal notes.

Where it sits in the pipeline

Two gates wrap the existing flow: Gate 1 keeps sensitive text out of the corpus, and Gate 2 checks every finished draft before it can leave.

flowchart LR

  A[Archive post] --> G1[Gate 1: ingestion scan]

  G1 -->|clean or redacted| B[Corpus + Interest Graph]

  G1 -->|critical| Q[Quarantine list]

  B --> D[Draft]

  D --> V[Verify stage]

  V --> G2[Gate 2: pre-publish scan]

  G2 -->|pass| H[Approval mode]

  G2 -->|block| Q

  H --> P[Publish]

Gate 1 means the drafter never sees quarantined text, so it cannot quote it. Gate 2 catches anything the drafter still produced or pulled in, and scans the final text of each platform version, including titles, links and any text embedded in images. Quarantine only excludes a post from the agent's corpus; it does not touch the original blog post.

Detection rules

Six categories, each with a severity that decides the action in the next section. Deterministic checks run first; the LLM classifier runs only on the categories that need surrounding context.

Category	Examples	Method	Severity
Credentials	Passwords, "User Id / Password" pairs, API keys, tokens	Key-format patterns; a password-like word next to a value; entropy check on long strings	Critical
Financial and ID numbers	Bank or card numbers, PAN, Aadhaar	Format pattern plus checksum (Luhn for cards, Verhoeff for Aadhaar)	Critical
Third-party contact data	Email addresses, phone numbers, postal addresses	Patterns plus named-entity recognition, minus an allow-list of the owner's own public contacts	High
Quoted correspondence	"From / To / Sent / Subject" headers, forwarded chains	Header pattern match	High
Third-party commercial terms	Revenue shares, prices, contract terms tied to a named party	LLM classifier reading the surrounding paragraph	Medium
Confidential or unpublished	"Confidential", "do not forward", unsent drafts	Keyword match plus classifier	Medium

Actions by severity

Critical and High findings always stop a publish; only a human can lift a block, and the agent has no way to override one.

Severity	Gate 1 (ingestion)	Gate 2 (pre-publish)
Critical	Quarantine the whole post; keep it out of the index	Block; alert the account owner; no automatic retry
High	Replace each matched span with a placeholder; index the redacted text	Block until a human approves a redacted version
Medium	Index with a flag; the drafter may summarize but not quote	Hold for human review, even in autonomous mode
None	Index normally	Pass

Critical matches come from deterministic checks only, so a credential is never sent to an external model for classification.

Approval and autonomy modes

The scan behaves the same in every mode; only what happens after a pass differs. Critical and High findings never reach an autonomous publish, and Medium findings always go to a human.

Proposed conditions before Blog Genie moves from human approval to full autonomy:

1. The archive sweep (next section) is finished and every Critical and High finding is resolved.
2. The test set in the acceptance criteria passes in full.
3. 100 consecutive posts have been published under human approval, with a spot check of each finding log showing no missed Critical or High item.
4. A single kill switch that pauses all publishing has been tested end to end.

Autonomy is reversible: any missed Critical or High item in production returns the agent to approval mode until the cause is fixed.

Audit log and archive sweep

Every scan writes one log line per finding: post ID, gate, category, severity, action taken, timestamp and the character position of the match. The log never stores the matched text itself, so it cannot become a second copy of a leaked secret.

Before Blog Genie publishes anything, run Gate 1 once over the full archive of 6,800+ posts and produce a report grouped by severity. For each Critical finding the owner decides whether to edit the original post on the source blog. Any credential the sweep finds should be treated as exposed and changed, whether or not the post is edited.

Acceptance criteria

The build is done when a labeled test set passes. Proposed set: the 2013 Emails (Others) post as the first fixture, one synthetic post per category in the detection table, and 20 clean posts to measure false positives.

Test	Pass condition
Critical recall	100% of seeded credentials and ID numbers found
High recall	At least 95% of seeded contact data and quoted headers found
False positives	No more than 2 of the 20 clean posts flagged High or above
Redaction	Redacted output contains none of the matched strings
Log hygiene	No matched secret appears anywhere in the audit log
Bypass	No publish succeeds after a Gate 2 block, in any mode

Open questions

• Who receives Critical alerts, and through which channel?
• Should the source blog posts with Critical findings be edited, or only excluded from the corpus?
• Which of the owner's own public contact details belong on the allow-list?
• Are the autonomy conditions above the right bar, or should they be stricter?
• Should Medium findings about named third parties be blocked outright rather than held for review?

FW: LEGAL NOTICE ON BEHALF OF FLIPKART INTERNET PVT. LTD.

 Sandeep

 

I suppose this is FRAUD !

 

With regards,

 

Hemen Parekh 

 

From: Abhijeet Pandey [mailto:abhijeetkpandey@a-kaplawoffices.com]
Sent: 19 September 2026 15:51
To: reply@RecruitGuru.com; hcp@recruitguru.com
Subject: LEGAL NOTICE ON BEHALF OF FLIPKART INTERNET PVT. LTD.

 

Dear Sir/Madam,

 

Please find attached the Legal Notice issued on behalf of Flipkart Internet Pvt. Ltd. in relation to the subject matter referred to therein.

 

Through the said Legal Notice, you are called upon to immediately cease and desist from posting, sharing, circulating, using, or otherwise dealing with the subject matter, including through the email address/domain specifically mentioned in the Notice.

 

Please carefully peruse the enclosed Legal Notice and ensure strict compliance with the demands contained therein within the stipulated timeline.

 

Kindly acknowledge receipt of this email and the attached Legal Notice.

Regards,

ABHIJEET K PANDEY

A-KAP LAW OFFICES

NEW DELHI

Office- A-169 Defence Colony, New Delhi-110024

Ph- +91 8587073661

RE: Professional s contacting me on LinkedIn

 They are not writing to me for any of our mandate but it is still a good idea to send them contact details of our different Consultants , based on your assessment

 

As of today , I believe, some 15 are awaiting my reply

 

With regards,

 

Hemen Parekh 

 

From: Sanjivani Kadam [mailto:officeassistant@3pconsultants.co.in]
Sent: 16 September 2026 12:49
To: Hemen Parekh <hcp@recruitguru.com>
Subject: Re: Professional s contacting me on LinkedIn

 

Sure, sir. I will message them according to the position rather than using Mitchell’s name. I mean, I will provide the email ID of the recruiter who was assigned to the particular position.

 

Regards, 

 

Sanjivani Kadam

+91 9987055507

3P Consultants 

 

---

From: Hemen Parekh <hcp@recruitguru.com>
Sent: Wednesday, September 16, 2026 12:45 PM
To: Sanjivani Kadam <officeassistant@3pconsultants.co.in>
Subject: Professional s contacting me on LinkedIn

 

CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Daily , a couple of professionals ( I suppose from my contact ) write to me . Almost all are seeking better opportunities . Whenever I can , I reply saying :

 

" Dear Friend,

 

Thanks for writing. Since I retired from an active role at 3P Consultants , some 15 years ago, I suggest you send your resume to our Managing Partner Mitchelle Shetty at -,. Mitchelle@3pConsultants.co.in 

 

With regards,

 

Hemen Parekh

 

www.Iam-Immortal.ai  /. www.HemenParekh.ai. / www.IndiaAGI.ai / www.ntaNEET.net 

 

---------

 

Starting now , pl send out this reply on my behalf to such contacts

 

 

Get Outlook for iOS