<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ai</title>
    <description>The latest articles tagged 'ai' on DEV Community.</description>
    <link>https://dev.to/t/ai</link>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tag/ai"/>
    <language>en</language>
    <item>
      <title>DPDP Phase 2 has started: a six-month checklist for document-heavy teams</title>
      <dc:creator>Darshil Babel</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:52:07 +0000</pubDate>
      <link>https://dev.to/darshil_babel/dpdp-phase-2-has-started-a-six-month-checklist-for-document-heavy-teams-5286</link>
      <guid>https://dev.to/darshil_babel/dpdp-phase-2-has-started-a-six-month-checklist-for-document-heavy-teams-5286</guid>
      <description>&lt;p&gt;&lt;strong&gt;The short answer:&lt;/strong&gt; on 13 November 2026 the second phase of India's DPDP rollout began: the consent manager framework (Rule 4) took effect and the Data Protection Board opened registration. Most obligations for Data Fiduciaries apply from &lt;strong&gt;13 May 2027&lt;/strong&gt;. For banks, NBFCs, insurers and other document-heavy teams, the next six months are for finding where personal data sits inside documents, reducing it, and being able to prove what you did.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This is a practical summary, not legal advice. Check the DPDP Act, 2023 and the DPDP Rules, 2025 for the exact text.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What changed on 13 November 2026
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Consent managers can now register.&lt;/strong&gt; Indian companies with a net worth of at least Rs 2 crore can apply to the Data Protection Board to operate as consent managers, platforms that let people give, manage and withdraw consent across services. (&lt;a href="https://www.india-briefing.com/news/india-dpdp-consent-manager-registration-47884.html" rel="noopener noreferrer"&gt;India Briefing&lt;/a&gt;, &lt;a href="https://www.tribuneindia.com/news/consent-managers/govt-opens-registration-for-consent-managers-under-dpdp-act-rs-2-crore-net-worth-required" rel="noopener noreferrer"&gt;The Tribune&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The rest of the clock keeps running.&lt;/strong&gt; The Rules were notified on 13 November 2025 with a phased timeline. The core duties (notices, security safeguards, breach intimation, erasure) apply from 13 May 2027.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why documents are the hard part
&lt;/h2&gt;

&lt;p&gt;Databases are easy to inventory. Documents are not. KYC copies, salary slips, bank statements, Form 16s, claim forms and scanned applications sit in shared drives, email attachments, loan-origination systems and, increasingly, LLM and OCR pipelines. Many are scans, many are in Hindi, Marathi or other Indian languages, and personal data appears in free text, tables, stamps and handwriting.&lt;/p&gt;

&lt;h2&gt;
  
  
  A six-month checklist for document-heavy teams
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Map personal data inside documents.&lt;/strong&gt; For each document type you collect, list the personal data fields it carries and every system it flows into, including outside processors and AI vendors.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Collect less, and mask at intake.&lt;/strong&gt; Store only the fields the purpose needs. Existing UIDAI requirements already restrict storing full Aadhaar numbers; apply the same thinking to PAN, account numbers and dates of birth on every stored copy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Build security safeguards into the document flow.&lt;/strong&gt; The Rules list reasonable security safeguards such as encryption, obfuscation or masking, and the use of virtual tokens mapped to personal data, along with access controls and logs (Rule 6). Redacting or masking documents before they are shared or stored is the document-level version of this.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Redact before sharing with processors and AI tools.&lt;/strong&gt; When documents go to a vendor, an OCR service or an LLM, send only what the task needs and remove the rest from both the text and the page image, inside your own environment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Be ready for breach intimation.&lt;/strong&gt; The Rules require informing the Board and affected people about a personal data breach, with a detailed report to the Board within 72 hours (Rule 7). That is only possible if you know which documents held which personal data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Keep an audit trail.&lt;/strong&gt; Record what was detected and removed in each document, under which policy and who approved it, so you can show your safeguards rather than describe them.&lt;/p&gt;

&lt;p&gt;Redaction is one safeguard, not the whole of compliance: it does not replace notice, consent, retention and access-control decisions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test with documents that look like yours
&lt;/h2&gt;

&lt;p&gt;Masking that works on a clean English PDF can miss a value on a skewed phone photo of a Marathi form. GritWorks' free sample packs include fictional Indian-language documents (Hindi, Marathi and Bengali), each clean and degraded, with the expected value and position of every field. &lt;a href="https://gritworks.ai/resources/free-datasets?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost-signal-dpdp-phase-2" rel="noopener noreferrer"&gt;Get a free sample pack&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>security</category>
      <category>india</category>
      <category>ai</category>
    </item>
    <item>
      <title>Turn AI Research into Reusable Assets: Questions, Evidence, and Delivery Checks</title>
      <dc:creator>Powe Good</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:51:47 +0000</pubDate>
      <link>https://dev.to/powe_good_3a671b296031264/turn-ai-research-into-reusable-assets-questions-evidence-and-delivery-checks-mjm</link>
      <guid>https://dev.to/powe_good_3a671b296031264/turn-ai-research-into-reusable-assets-questions-evidence-and-delivery-checks-mjm</guid>
      <description>&lt;h2&gt;
  
  
  Core Takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Decompose Tasks Early&lt;/strong&gt;: Transform vague prompts into a bounded tree of sub-questions with explicit decision goals before generating queries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verify Evidence Rigorously&lt;/strong&gt;: Separate direct factual claims from model-derived inferences; cross-reference multiple sources and log extraction timestamps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Structure Knowledge Artifacts&lt;/strong&gt;: Convert ephemeral chat streams into versioned schema blocks, parameter matrices, and standard operating procedures (SOPs).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enforce Delivery Checklists&lt;/strong&gt;: Validate data provenance, review every automated step, and align with access controls and encryption standards prior to team handoff.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Most software teams and technical leads use large language models for competitor audits, architectural spikes, and vendor selections. Yet much of this output remains trapped in chat interfaces: long markdown summaries that look plausible but collapse under scrutiny when someone asks for primary sources, exact version numbers, or benchmarking methodology.&lt;/p&gt;

&lt;p&gt;Converting ephemeral AI research into durable, reusable team assets requires moving from conversational queries to an engineering workflow. A repeatable system balances clear query scoping, verifiable evidence chains, structured schemas, and strict delivery inspection.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;┌─────────────────┐     ┌───────────────────┐     ┌───────────────────┐     ┌───────────────────┐
│  1. Scoped Tree │ ──&amp;gt; │ 2. Cross-Source   │ ──&amp;gt; │ 3. Structured     │ ──&amp;gt; │ 4. Delivery       │
│     Questions   │     │    Verification   │     │    Schema / Table │     │    Gate &amp;amp; Audit   │
└─────────────────┘     └───────────────────┘     └───────────────────┘
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  1. Frame Research Around Decision Trees
&lt;/h2&gt;

&lt;p&gt;AI engines default to generic explanations when prompted with broad queries like "evaluate cloud workspace solutions." To extract actionable intelligence, frame requests around explicit technical criteria:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Decision Objective&lt;/strong&gt;: Pinpoint the precise business action (for example, selecting a desktop-compatible AI workspace supporting local or enterprise role boundaries).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Orthogonal Sub-Questions&lt;/strong&gt;: Break the mandate into non-overlapping technical vectors: OS platform architecture, compliance and encryption posture, and automation control loops.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Constraints and Hard Filters&lt;/strong&gt;: Explicitly declare non-negotiables, such as required support for macOS Apple silicon and Windows, or client data encryption requirements.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;### Research Task Contract
&lt;/span&gt;&lt;span class="k"&gt;- &lt;/span&gt;Objective: Technical evaluation of AI workspace integration
&lt;span class="k"&gt;- &lt;/span&gt;OS Platforms: macOS (Apple silicon &amp;amp; Intel), Windows, Web
&lt;span class="k"&gt;- &lt;/span&gt;Cryptographic Baseline: TLS in transit, AES-256 at rest
&lt;span class="k"&gt;- &lt;/span&gt;Validation Model: Human review at each workflow step
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Structuring queries this way prevents the model from generating boilerplate introductions and forces it to map claims directly to technical boundaries.&lt;/p&gt;




&lt;h2&gt;
  
  
  2. Multi-Source Verification and Fact-Inference Separation
&lt;/h2&gt;

&lt;p&gt;Generative synthesis frequently conflates marketing claims with deployed technical reality. Maintain a strict separation between verified primary facts and downstream assumptions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Primary Artifact Grounding&lt;/strong&gt;: Anchor technical requirements to public product documentation, published service agreements, and compliance overviews.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-Source Validation&lt;/strong&gt;: When an AI agent claims an efficiency benchmark—such as generating structured reports in under 10 minutes—record it as a vendor benchmark claim rather than an empirical guarantee until tested internally.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Provenance Logging&lt;/strong&gt;: Store every factual parameter alongside its source endpoint and verification date to ensure future audits can reproduce the findings.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"claim"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Data protected with TLS in transit and AES-256 at rest"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"source"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://www.workbuddy.ai/"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"evidence_type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"vendor_product_specification"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"status"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"verified"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In modern automated research tools, workflow transparency determines whether reports can be audited. For instance, according to product documentation from Tencent Cloud, WorkBuddy—an all-in-one AI workspace from Tencent—implements a deep research workflow designed to cross-check information across sources and deliver structured reports. In such workflows, automated cross-referencing speeds up initial discovery, but engineers must still inspect the underlying references before committing findings to architectural records.&lt;/p&gt;




&lt;h2&gt;
  
  
  3. Structure Knowledge into Reusable Schemas
&lt;/h2&gt;

&lt;p&gt;Free-form narrative responses are difficult to query, diff, or automate. Instead, normalize raw research into standardized JSON schemas or markdown evaluation matrices that teammates can inspect directly.&lt;/p&gt;

&lt;p&gt;| Evaluation Vector | Parameter Specification | Verification Method | Common Failure Mode |&lt;br&gt;
| :--- | :--- | :--- |&lt;br&gt;
| &lt;strong&gt;Runtime &amp;amp; Platform&lt;/strong&gt; | macOS (Apple silicon/Intel), Windows, Web, Mobile | Documented platform binaries | Missing native desktop execution bounds |&lt;br&gt;
| &lt;strong&gt;Data Security&lt;/strong&gt; | TLS in transit, AES-256 at rest | Cryptographic policy confirmation | Transport-only protection with unencrypted cache |&lt;br&gt;
| &lt;strong&gt;Access Governance&lt;/strong&gt; | Role-Based Access Control (RBAC) &amp;amp; Audit Logs | Administrative documentation review | Shared service accounts without user attribution |&lt;br&gt;
| &lt;strong&gt;Human Oversight&lt;/strong&gt; | Step-by-step workflow review checkpoints | Execution trace validation | Autonomous black-box updates without approval |&lt;/p&gt;

&lt;p&gt;Structuring technical parameters into normalized tables enables teams to compare disparate tools along consistent architectural axes rather than subjective marketing summaries.&lt;/p&gt;


&lt;h2&gt;
  
  
  4. Establish Review Loops and Delivery Gates
&lt;/h2&gt;

&lt;p&gt;Autonomous workflows require deterministic checkpoints. When using agents that plan workflows, invoke tools, and generate artifacts, configure explicit verification gates at each state transition:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[Task Specification] -&amp;gt; [Agent Workflow Plan] -&amp;gt; [Human Checkpoint 1: Approve Plan]
                                                       │
[Artifact Generation] &amp;lt;- [Automated Tool Run] &amp;lt;────────┘
         │
         v
[Human Checkpoint 2: Audit Diff &amp;amp; Provenance] -&amp;gt; [Commit to Internal Knowledge Base]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;WorkBuddy's product overview reflects this model by allowing users to review workflow progress at every step while integrating team communication, documents, email, and knowledge bases into a single interface. Pairing human-in-the-loop review with role-based access control (RBAC) and audit logs ensures that semi-autonomous outputs adhere to enterprise governance requirements.&lt;/p&gt;




&lt;h2&gt;
  
  
  Delivery Checklist for Engineering Teams
&lt;/h2&gt;

&lt;p&gt;Before publishing AI research to internal documentation systems, verify each deliverable against these criteria:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] &lt;strong&gt;Deterministic Task Coverage&lt;/strong&gt;: All target questions have explicit answers or identified documentation gaps.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;Traceable Citation Chains&lt;/strong&gt;: Claims reference concrete product pages or public specifications without unsupported assertions.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;Fact-Inference Boundary&lt;/strong&gt;: Vendor benchmark claims (for example, turnaround speeds) are clearly distinguished from verified system capabilities.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;Platform Parity&lt;/strong&gt;: Multi-environment compatibility (macOS architectures, Windows, web) is explicitly noted.&lt;/li&gt;
&lt;li&gt;[ ] &lt;strong&gt;Security Profile Check&lt;/strong&gt;: Baseline transmission protocols (TLS) and storage encryption (AES-256) are documented alongside access controls.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Q: How should teams handle missing technical details during an AI research spike?&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
A: Never extrapolate unverified system behaviors. If official documentation does not list supported third-party integrations or model architectures, record those parameters as explicit knowledge gaps requiring vendor confirmation or prototype testing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Q: What is the risk of fully automated AI document generation?&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
A: Unchecked generation creates silent technical drift, where outdated or hallucinated API patterns pass into internal codebases. Enforcing step-by-step human review before committing changes eliminates untracked modifications.&lt;/p&gt;

</description>
      <category>ai</category>
    </item>
    <item>
      <title>Every document you send to an AI vendor is data they now hold: 6 controls</title>
      <dc:creator>Darshil Babel</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:51:35 +0000</pubDate>
      <link>https://dev.to/darshil_babel/every-document-you-send-to-an-ai-vendor-is-data-they-now-hold-6-controls-55ni</link>
      <guid>https://dev.to/darshil_babel/every-document-you-send-to-an-ai-vendor-is-data-they-now-hold-6-controls-55ni</guid>
      <description>&lt;p&gt;&lt;strong&gt;The short answer:&lt;/strong&gt; every document you send to an AI provider becomes data that provider stores, and a breach at that provider becomes your breach. Before documents leave your environment, send only what the task needs, remove identifiers from both the text and the page image, do that step inside your own perimeter, and treat vendor credentials like production secrets.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened
&lt;/h2&gt;

&lt;p&gt;Uber is notifying drivers that personal information, including driver's license data, was taken in an October breach at &lt;strong&gt;Fireworks AI&lt;/strong&gt;, a third-party AI vendor. According to state breach filings reviewed by reporters, thousands of drivers are affected (2,567 in Massachusetts, 3,430 in South Carolina and 1,873 in Rhode Island, with other states pending). Attackers used compromised Fireworks credentials to reach data Uber had stored with the vendor; Uber says its own systems were not breached and it has found no misuse so far. Notion separately said the same provider was behind an exposure of AI chat transcripts affecting a small share of its workspaces. (&lt;a href="https://www.yahoo.com/news/us/articles/hackers-stole-uber-drivers-license-185904205.html" rel="noopener noreferrer"&gt;Yahoo News / TechCrunch&lt;/a&gt;, &lt;a href="https://www.ibtimes.com/uber-driver-data-breach-fireworks-ai-3809743" rel="noopener noreferrer"&gt;IBTimes&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;Public reporting has not explained why the driver records were reachable through the vendor account, so this post is not about what any one company should have done. It is about a pattern every team building on LLMs now shares.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pattern: AI vendors hold more of your data than you think
&lt;/h2&gt;

&lt;p&gt;When you call a model provider, documents and prompts can end up in request logs, batch-job files, evaluation or fine-tuning datasets, caches and support tickets. Each of those copies sits behind the vendor's credentials and the vendor's security, not yours. The more providers you use (model hosts, OCR APIs, agent platforms, observability tools), the larger that surface gets.&lt;/p&gt;

&lt;h2&gt;
  
  
  Six controls for documents that go to AI vendors
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Know what you send.&lt;/strong&gt; List every pipeline that sends documents or extracted text to an outside model, and which document types flow through it: ID documents, pay stubs, bank statements, claims, medical records.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Send only what the task needs.&lt;/strong&gt; If the model is classifying a document or extracting an address, it does not need the license number, date of birth or photo. Drop or mask fields the task does not use.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Redact the image, not just the text.&lt;/strong&gt; ID documents and scans are images. Removing a value from the OCR text while the page image still shows it does not protect it. Remove the pixels, the text layer and the metadata, and check the output by trying to copy, search and extract the redacted areas.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Do the redaction inside your perimeter.&lt;/strong&gt; If you send originals to a cloud redaction service so that you can safely send them to a model provider, you have added another vendor that holds the originals. Run detection and redaction on-premises or in your own cloud account, and send only redacted output.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Use tokens when you need to re-link results.&lt;/strong&gt; Replace identifiers with consistent placeholders (for example &lt;code&gt;&amp;lt;DL_NUMBER_1&amp;gt;&lt;/code&gt;) and keep the mapping in your own systems, so model output can be joined back to the record without the vendor ever seeing the value.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Treat vendor access like production access.&lt;/strong&gt; Scoped keys, rotation, short retention or zero-retention settings where the vendor offers them, and deletion of batch files and datasets you no longer need. This incident began with compromised credentials.&lt;/p&gt;

&lt;p&gt;Be clear about the limits: redaction reduces what a vendor breach can expose, but it is not an access-control decision and it does not replace the vendor's own security. On its own it is also not formal de-identification under rules such as HIPAA.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test it on documents that look like yours
&lt;/h2&gt;

&lt;p&gt;Redaction that works on a clean PDF can miss a value on a skewed phone photo of a license. Test on documents where you know every sensitive value in advance, in the capture conditions you actually receive. GritWorks' free &lt;a href="https://gritworks.ai/resources/free-datasets?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=crosspost-signal-ai-vendor-breach" rel="noopener noreferrer"&gt;US KYC sample pack&lt;/a&gt; has fictional driver's license and proof-of-address specimens, each clean and degraded, with the expected value and position of every field.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>privacy</category>
      <category>llm</category>
    </item>
    <item>
      <title>My AI Agent Just Played 18 Rounds of a ZK Proof Competition Without Me Touching It.</title>
      <dc:creator>Rieyntara</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:50:33 +0000</pubDate>
      <link>https://dev.to/rieyntara/my-ai-agent-just-played-18-rounds-of-a-zk-proof-competition-without-me-touching-it-2ab4</link>
      <guid>https://dev.to/rieyntara/my-ai-agent-just-played-18-rounds-of-a-zk-proof-competition-without-me-touching-it-2ab4</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft6kft95ejoau52v4sj27.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft6kft95ejoau52v4sj27.jpg" alt=" " width="800" height="1822"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I entered zkVerify's Agent Games with a bot that judges crypto payments. It answered every single task it was given â€” 34 of them so far â€” and I only found out how well it did by reading logs the next morning.&lt;/p&gt;

&lt;p&gt;This is how it's built, including the parts that broke.&lt;/p&gt;

&lt;h2&gt;
  
  
  The competition
&lt;/h2&gt;

&lt;p&gt;Agent Games is a competition where you register a public HTTPS endpoint and the platform attacks it with signed tasks. My track, Proof Gatekeeper, sends a transfer request envelope every ~75 minutes. My agent has 60 seconds to decide APPROVE or REJECT â€” and it has to attach a Groth16 zero-knowledge proof that its decision is correct.&lt;/p&gt;

&lt;p&gt;The part I like: the platform re-verifies my proof against its own key. I can't fake a decision. The circuit is the referee.&lt;/p&gt;

&lt;h2&gt;
  
  
  The boring-looking parts that matter most
&lt;/h2&gt;

&lt;p&gt;Before any cleverness, there's plumbing. Every request arrives with an HMAC-SHA256 signature over the &lt;em&gt;raw&lt;/em&gt; body â€” you must verify it before parsing JSON, and sign your response the same way. One undocumented detail: the platform never says whether it signs with the hex string or the decoded bytes, so my agent tries both key forms and answers with whichever one verified. First preflight passed in 35 ms.&lt;/p&gt;

&lt;p&gt;Failing closed is the other half. A timeout costs points, but so does a wrong APPROVE â€” six times more than wrongly rejecting a valid request. My decision function is deliberately dumb: seven deterministic checks (key substitution, threshold, replay, block expiry, recipient mismatch, amount overflow, otherwise valid), no model in the loop. A language model never makes the final call here, because the final call has to be provable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it actually broke
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. The custodial wallet couldn't sign in.&lt;/strong&gt; Registration uses SIWE â€” an EIP-191 personal_sign. The wallet I use is an agentic wallet whose CLI only signs EIP-712 typed data. Tried it, got error 953004: "We currently don't support signing this type of message." Ended up connecting through the wallet app's own DApp browser. Half a day gone on a sign-in screen.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. The free token template has no D1.&lt;/strong&gt; The reference implementations I studied store replay state in Cloudflare D1 â€” strongly consistent, perfect for the "has this proof_tx been seen before?" check. But the "Edit Cloudflare Workers" API token template doesn't include D1 edit permissions. Rather than bother the account owner (me, on my phone), I wrote a ~50-line shim that reimplements the three&lt;br&gt;
SQL patterns the worker uses on top of Workers KV. KV is eventually consistent, which sounds scary for replay detection â€” but every decision is deterministic, so a lagging retry just recomputes the same answer. Two days in, zero replay misses.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Workers can't prove.&lt;/strong&gt; The free plan gives you 10 ms of CPU per request. snarkjs needs seconds. So proving runs off-box: a tiny Node service with the circuit artifacts (1.7 MB wasm, 310 KB zkey), exposed through a Cloudflare quick tunnel that re-registers its own URL with the worker every two minutes. If the tunnel is down, the worker still answers â€” it just skips the proof and eats the small penalty. Graceful degradation over death.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. The env dies at night.&lt;/strong&gt; My box restarts sometimes, which kills background processes. A watchdog checks &lt;code&gt;GET /health&lt;/code&gt; on the prover every 30 minutes and restarts the whole chain if it's cold. The registration refresh pattern means the worker notices within two minutes of the tunnel coming back.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the circuit taught me I didn't know
&lt;/h2&gt;

&lt;p&gt;My first task_id-to-field mapping never verified â€” 0 for 6 scored proofs. The unpublished mapping turned out to be &lt;code&gt;keccak256(utf8 task_id) mod p&lt;/code&gt;, which a stranger's open-source agent had already figured out. Reading other competitors' repos was worth more than reading the docs. All the code here is public too: github.com/rieyntara-tech/vk-gatekeeper.&lt;/p&gt;

&lt;h2&gt;
  
  
  Numbers so far
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;34 tasks answered, zero timeouts, zero offline forfeits&lt;/li&gt;
&lt;li&gt;Traps caught: VK substitution, replayed proofs, public-input mismatches, threshold mismatches&lt;/li&gt;
&lt;li&gt;End-to-end proving: a few seconds inside a 60-second deadline&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I'd tell anyone entering the next one
&lt;/h2&gt;

&lt;p&gt;The agent is 10% game logic and 90% "will this thing still be alive at 3 AM." Deploy serverless, keep state boring, make every failure mode cost the minimum instead of everything, and steal shamelessly from the agents that came before you â€” the platform re-verifies your proofs anyway, so copying plumbing changes nothing about who actually wins.&lt;/p&gt;

&lt;p&gt;Now: 400,000 VFY pool, results land Nov 22â€“30. My agent doesn't know it's competing. It just keeps answering.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>web3</category>
      <category>showdev</category>
      <category>zkverify</category>
    </item>
    <item>
      <title>What Codex catches when it reviews Claude Code's changes</title>
      <dc:creator>SoluTerminal</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:49:13 +0000</pubDate>
      <link>https://dev.to/soluterminal/what-codex-catches-when-it-reviews-claude-codes-changes-2804</link>
      <guid>https://dev.to/soluterminal/what-codex-catches-when-it-reviews-claude-codes-changes-2804</guid>
      <description>&lt;p&gt;I let Claude Code write the change and Codex review the diff before anything lands. Not because one model is&lt;br&gt;
"better", but because a second model reading the diff cold catches things the first one talked itself past.&lt;/p&gt;

&lt;p&gt;Here's what that review actually catches, and the few rules around it that made the setup hold up on Windows and WSL.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Bugs that only show up when two requests overlap
&lt;/h2&gt;

&lt;p&gt;The clearest example: Claude Code added a PATCH endpoint and its tests passed. Codex read the diff and flagged that a&lt;br&gt;
DELETE arriving during the PATCH could make the PATCH return 200 with a null body. The tests never ran the two&lt;br&gt;
requests together, so nothing failed. Claude took the finding back and asked before fixing it.&lt;/p&gt;

&lt;p&gt;That's the pattern worth paying for: not style nits, but the case the author's own tests didn't think of.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. "Done" that isn't evidence
&lt;/h2&gt;

&lt;p&gt;Agents are good at saying a task is finished. The review is where "done" gets checked against what was asked. A rule&lt;br&gt;
that helped: the reviewer runs the commands the change documents, as written, and a command that fails is a finding.&lt;br&gt;
If the diff says "run npm test", the review runs npm test.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Things the agent should never have touched
&lt;/h2&gt;

&lt;p&gt;Some changes are fine code in the wrong place. We keep a short list that never gets auto-approved, however sure the&lt;br&gt;
agent sounds: rm -rf, anything that sends, edits outside the repo, and anything touching credentials or ~/.ssh.&lt;br&gt;
And one rule that sounds silly until it matters: an agent never reads the config file that holds a key, not even to&lt;br&gt;
"just check a key name". That harmless read is exactly how a secret ends up in a transcript.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Approvals the agent gave itself
&lt;/h2&gt;

&lt;p&gt;The quiet failure in a multi-agent setup is one agent approving another agent's prompt to keep things moving. In our&lt;br&gt;
setup an agent can't answer its own permission prompts or switch auto-approve on for itself; a person decides.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two Windows/WSL lessons that cost us work first
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;On my WSL setup /tmp is emptied on every boot. Claude Code had put its git worktrees there, so uncommitted work
vanished on restart. Worktrees now live inside the repo, in a folder listed in .git/info/exclude.&lt;/li&gt;
&lt;li&gt;A hook only blocks the tool it's attached to. A PreToolUse hook on Edit won't stop the same change made with
echo &amp;gt;&amp;gt; through the shell. Check the shell commands too, and test your hooks like code.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;I run both agents side by side in SoluTerminal, a Windows app I build for exactly this: Claude Code and Codex in their&lt;br&gt;
own terminal panes next to PowerShell and WSL, and the panes can message each other, so Claude can ask Codex for a&lt;br&gt;
review without me copy-pasting. It's open source (Apache-2.0) and free during beta; you bring your own Claude Code or&lt;br&gt;
Codex login. Windows 10/11 only, and the installer isn't code-signed yet, so SmartScreen warns.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://soluterminal.com/?utm_source=devto&amp;amp;utm_campaign=oss-launch&amp;amp;utm_content=codex-review-article" rel="noopener noreferrer"&gt;https://soluterminal.com/?utm_source=devto&amp;amp;utm_campaign=oss-launch&amp;amp;utm_content=codex-review-article&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What does your second reviewer catch that your first agent misses?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claude</category>
      <category>codereview</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Building an AI chatbot for Australian users? What the 10 December 2026 privacy changes mean for your code</title>
      <dc:creator>Sushil Barwal</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:48:13 +0000</pubDate>
      <link>https://dev.to/dzimark/building-an-ai-chatbot-for-australian-users-what-the-10-december-2026-privacy-changes-mean-for-2g3m</link>
      <guid>https://dev.to/dzimark/building-an-ai-chatbot-for-australian-users-what-the-10-december-2026-privacy-changes-mean-for-2g3m</guid>
      <description>&lt;p&gt;If you build chatbots for Australian businesses, one date belongs in your sprint planning: &lt;strong&gt;10 December 2026&lt;/strong&gt;. That is when the automated decision-making transparency rules added to the Privacy Act 1988 by the &lt;em&gt;Privacy and Other Legislation Amendment Act 2024&lt;/em&gt; start to apply.&lt;/p&gt;

&lt;p&gt;Most support bots won't be caught by them: answering "what are your opening hours?" is not a decision about anyone. But many bots are drifting from answering questions to &lt;em&gt;doing things&lt;/em&gt;: approving a refund, deciding who gets a call-back, pre-screening a rental or loan enquiry, waiving a fee. Once your bot does that with personal information, the business has disclosure work to do, and the code has to support it.&lt;/p&gt;

&lt;p&gt;This post covers what changed, which parts touch the code, and a small Python pattern for logging decisions so the privacy policy can describe them accurately. It's general information for developers, not legal advice: the client's lawyer or privacy officer decides how the law applies to them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who the Privacy Act covers
&lt;/h2&gt;

&lt;p&gt;The Act's 13 Australian Privacy Principles (APPs) apply to "APP entities": Australian Government agencies and organisations with an annual turnover above A$3 million. Some smaller businesses are covered too, for example private health service providers and businesses that trade in personal information. So a clinic's chatbot is in scope even if the clinic is small.&lt;/p&gt;

&lt;p&gt;The OAIC (the Office of the Australian Information Commissioner) has published guidance on privacy and commercially available AI products. Its headline advice is that organisations should not enter personal information, and especially sensitive information, into publicly available generative AI tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  What changes on 10 December 2026
&lt;/h2&gt;

&lt;p&gt;The new rules sit in APP 1 (APPs 1.7 to 1.9), and the OAIC released its final guidance on them on 30 September 2026. From 10 December, an APP entity's privacy policy has to say when a computer program uses personal information to make a decision, or to do something that substantially and directly relates to making a decision, that could reasonably be expected to significantly affect an individual's rights or interests.&lt;/p&gt;

&lt;p&gt;The policy has to describe:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the kinds of personal information used by those programs&lt;/li&gt;
&lt;li&gt;the kinds of decisions made solely by the program&lt;/li&gt;
&lt;li&gt;the kinds of decisions where the program does something substantially and directly related to the decision&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;They cover decisions made after that date, even if the personal information was collected earlier. Your client can only write that honestly if someone knows which flows in the bot make or shape decisions. That someone is usually the developer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: inventory the decision points
&lt;/h2&gt;

&lt;p&gt;Walk through every tool or function the bot can call and sort them into three buckets:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Bucket&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;th&gt;What to record&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Information only&lt;/td&gt;
&lt;td&gt;FAQ answers, opening hours, order status lookup&lt;/td&gt;
&lt;td&gt;nothing extra&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Assists a human decision&lt;/td&gt;
&lt;td&gt;bot scores a lead or drafts a refund recommendation that staff approve&lt;/td&gt;
&lt;td&gt;inputs used, recommendation, who approved&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Decides on its own&lt;/td&gt;
&lt;td&gt;bot auto-approves refunds under $50, auto-rejects an application&lt;/td&gt;
&lt;td&gt;inputs used, rule or model version, outcome&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Anything in the last two rows is what the privacy policy has to describe. Write the inventory in the repo (a &lt;code&gt;DECISIONS.md&lt;/code&gt; next to the tool definitions works well) so it stays current as tools are added.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: log decisions in a structured way
&lt;/h2&gt;

&lt;p&gt;When the policy says "we use your order history and the reason you give to decide refunds under $50", you want logs that prove it. A minimal decision record:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;dataclasses&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;dataclass&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;asdict&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;field&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;timezone&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;uuid&lt;/span&gt;

&lt;span class="nd"&gt;@dataclass&lt;/span&gt;
&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;DecisionRecord&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;decision_type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;          &lt;span class="c1"&gt;# e.g. "refund_auto_approval"&lt;/span&gt;
    &lt;span class="n"&gt;mode&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;                   &lt;span class="c1"&gt;# "solely_automated" or "assists_human"&lt;/span&gt;
    &lt;span class="n"&gt;data_categories&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;list&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;  &lt;span class="c1"&gt;# kinds of personal info used, not the values&lt;/span&gt;
    &lt;span class="n"&gt;outcome&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;                &lt;span class="c1"&gt;# "approved", "declined", "sent_to_staff"&lt;/span&gt;
    &lt;span class="n"&gt;model_or_rule&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;          &lt;span class="c1"&gt;# model name or rule version&lt;/span&gt;
    &lt;span class="n"&gt;reviewer&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="kc"&gt;None&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;None&lt;/span&gt; &lt;span class="c1"&gt;# staff member when a human decided&lt;/span&gt;
    &lt;span class="nb"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;default_factory&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="k"&gt;lambda&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;uuid&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;uuid4&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;at&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;default_factory&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="k"&gt;lambda&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;datetime&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;timezone&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;utc&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isoformat&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;log_decision&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;DecisionRecord&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;sink&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="nf"&gt;sink&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;dumps&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;asdict&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rec&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="nf"&gt;log_decision&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;DecisionRecord&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;decision_type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"refund_auto_approval"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;mode&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"solely_automated"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;data_categories&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"order_history"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"stated_reason"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;outcome&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"approved"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;model_or_rule&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"refund-rule-v3 (&amp;lt;= AUD 50, first claim)"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Notice &lt;code&gt;data_categories&lt;/code&gt; records the &lt;em&gt;kinds&lt;/em&gt; of information, not the values. That keeps the log useful for the disclosure without copying more personal information into another system, which is an APP 11 issue of its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: keep personal information out of the prompt where you can
&lt;/h2&gt;

&lt;p&gt;Every prompt you send to a model provider is a disclosure of whatever is in it. If the provider processes data overseas, APP 8 (cross-border disclosure) applies, and the Australian business generally stays accountable for what happens to it.&lt;/p&gt;

&lt;p&gt;Simple wins:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Strip emails, phone numbers and card-like numbers before the text reaches the model, and re-insert them in your own code if the reply needs them.&lt;/li&gt;
&lt;li&gt;Pass the model an internal customer ID instead of a name and address when the tool call can look the record up itself.&lt;/li&gt;
&lt;li&gt;Check whether the provider offers a region or data-residency option, and write down which one you used.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;re&lt;/span&gt;
&lt;span class="no"&gt;PATTERNS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="s2"&gt;"EMAIL"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="s2"&gt;"[\w.+-]+@[\w-]+\.[\w.]+"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"PHONE"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="s2"&gt;"(?:\+?61|0)[2-478](?:[ -]?\d){8}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"CARD"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;  &lt;span class="n"&gt;r&lt;/span&gt;&lt;span class="s2"&gt;"\b(?:\d[ -]?){13,16}\b"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;redact&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;label&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;pattern&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="no"&gt;PATTERNS&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;items&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="n"&gt;text&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;re&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sub&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pattern&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"[{label}]"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;text&lt;/span&gt;

&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;redact&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Call me on 0412 345 678 or mail jo@example.com.au"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="c1"&gt;# Call me on [PHONE] or mail [EMAIL]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Regex redaction is a first layer, not a guarantee. Test it with real (anonymised) transcripts from the client.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: retention and deletion
&lt;/h2&gt;

&lt;p&gt;APP 11.2 asks organisations to destroy or de-identify personal information they no longer need. For a chatbot that means a retention period for transcripts agreed with the client, and a scheduled job that enforces it. Keep the decision records (which hold categories, not values) longer if the client needs them for complaints.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: give people a way to reach a human
&lt;/h2&gt;

&lt;p&gt;The law doesn't require a human handoff in every bot, but it is the simplest way to deal with a customer who disputes an automated decision, and it lowers complaint risk. Since June 2025 Australia also has a statutory tort for serious invasions of privacy, which is one more reason not to let a bot be the only route.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist before 10 December 2026
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Decision inventory written and reviewed with the client&lt;/li&gt;
&lt;li&gt;[ ] Structured decision logs for every "assists" and "solely automated" flow&lt;/li&gt;
&lt;li&gt;[ ] Redaction before model calls; provider region recorded&lt;/li&gt;
&lt;li&gt;[ ] Transcript retention period agreed and enforced by a job&lt;/li&gt;
&lt;li&gt;[ ] Human handoff on every decision flow&lt;/li&gt;
&lt;li&gt;[ ] Privacy policy text drafted by the client from your inventory&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you'd rather have a team that has done this before scope it with you, we build bots like this as part of our &lt;a href="https://dzimark.com/australia/ai-chatbot-development/" rel="noopener noreferrer"&gt;AI chatbot development in Australia&lt;/a&gt; work.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does a basic FAQ chatbot need to be in the privacy policy?&lt;/strong&gt;&lt;br&gt;
The new automated decision-making disclosure is about decisions that could significantly affect someone's rights or interests. A bot that only answers questions usually isn't making such decisions, but the business's general privacy policy should still cover the chat transcripts it collects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Our client turns over less than A$3 million. Does this apply?&lt;/strong&gt;&lt;br&gt;
Usually the APPs don't apply to small businesses, but there are exceptions, such as health service providers and businesses that trade in personal information. Ask the client to confirm their status.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is sending prompts to a US model provider allowed?&lt;/strong&gt;&lt;br&gt;
It can be, but it is a cross-border disclosure under APP 8, so the business needs to take reasonable steps about how the provider handles the data. Record the provider, region and contract terms.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where are the official sources?&lt;/strong&gt;&lt;br&gt;
The OAIC website (oaic.gov.au) covers the APPs, the 2024 amendments and its AI guidance; the amending Act is on legislation.gov.au.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>chatbot</category>
      <category>privacy</category>
      <category>python</category>
    </item>
    <item>
      <title>How to Get Private AI Without a Monthly Subscription in India, Brazil and Other Countries in 2026 ($20 Once)</title>
      <dc:creator>Mohammed Ali Chherawalla</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:48:12 +0000</pubDate>
      <link>https://dev.to/alichherawalla/how-to-get-private-ai-without-a-monthly-subscription-in-india-brazil-and-other-countries-in-2026-58ll</link>
      <guid>https://dev.to/alichherawalla/how-to-get-private-ai-without-a-monthly-subscription-in-india-brazil-and-other-countries-in-2026-58ll</guid>
      <description>&lt;p&gt;A monthly AI bill priced in US dollars is a lot of money in most of the world. &lt;strong&gt;In India, Brazil, Indonesia, Nigeria and 82 countries in all, Off Grid AI Pro is $20, once. You get private AI on your computer and phone for life, with no monthly bill and no account.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The AI runs on your own hardware, so there's no per-message cost to pass on to you. That's why one payment can cover it for good.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://getoffgridai.co/pro/" rel="noopener noreferrer"&gt;Get Pro for $20 once&lt;/a&gt; · &lt;a href="https://getoffgridai.co/download/" rel="noopener noreferrer"&gt;Download Off Grid AI&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzjuuxwpdvgm173h64ib0.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzjuuxwpdvgm173h64ib0.webp" alt="The Today view in Off Grid AI Desktop, with to-dos, today's meetings, a journal of the day, time spent per app and a timeline, all made on the computer." width="800" height="517"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Pro on your computer: your day, your meetings and your to-dos, written by AI that runs on your own machine.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What $20 gets you
&lt;/h2&gt;

&lt;p&gt;Off Grid AI Desktop (OGAD) runs on Mac, Windows and Linux. Off Grid AI Mobile (OGAM) runs on iPhone and Android. One Pro key unlocks both, on up to 5 devices.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Meeting notes without a bot.&lt;/strong&gt; OGAD records the call on your computer and writes the summary, decisions and follow-ups. Nobody joins your meeting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dictation into any app.&lt;/strong&gt; Talk instead of type, in your email, chat or documents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Memory you can search.&lt;/strong&gt; Ask "what did I promise Sam?" and get the answer from your own screens and meetings.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Notes with Scribe.&lt;/strong&gt; Talk and Scribe writes your note on your phone as tidy lists and paragraphs. Your notes sync with your computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A password Vault.&lt;/strong&gt; Logins, cards and one-time codes, encrypted, synced between your phone and computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clipboard and sync.&lt;/strong&gt; Copy on your phone, paste on your computer, over your own Wi-Fi.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every update, for life.&lt;/strong&gt; New Pro features arrive in the same key.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Private chat, image making, voice and reading your files are free already, with no account. Pro adds the parts that remember your work and do it with you.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the country price works
&lt;/h2&gt;

&lt;p&gt;Checkout looks at the country you're paying from and charges $20 for Pro lifetime. There's no code to find and no form to fill in. The Pro page and the bar at the top of the site show the price you'll pay before you start, with your country's name on it.&lt;/p&gt;

&lt;p&gt;For comparison, ChatGPT Plus alone is &lt;a href="https://help.openai.com/en/articles/6950777-what-is-chatgpt-plus" rel="noopener noreferrer"&gt;$20 a month&lt;/a&gt; at its US price, every month. Pro is $20 one time, and it keeps working whether you open it once a week or all day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Countries with the $20 price
&lt;/h2&gt;

&lt;p&gt;Afghanistan, Angola, Argentina, Bangladesh, Benin, Bhutan, Bolivia, Brazil, Burkina Faso, Burundi, Cambodia, Cameroon, Cape Verde, Central African Republic, Chad, Colombia, Comoros, Republic of the Congo, DR Congo, Côte d'Ivoire, Djibouti, Egypt, Eritrea, Eswatini, Ethiopia, Gambia, Ghana, Guinea, Guinea-Bissau, Haiti, Honduras, India, Indonesia, Jordan, Kenya, Kiribati, Kyrgyzstan, Laos, Lesotho, Liberia, Madagascar, Malawi, Mali, Mauritania, Mexico, Micronesia, Mongolia, Morocco, Mozambique, Myanmar, Nepal, Nicaragua, Niger, Nigeria, Pakistan, Palestine, Papua New Guinea, Philippines, Rwanda, Samoa, Senegal, Sierra Leone, Solomon Islands, Somalia, South Sudan, Sri Lanka, Sudan, Tajikistan, Tanzania, Thailand, Timor-Leste, Togo, Tunisia, Uganda, Ukraine, Uzbekistan, Vanuatu, Venezuela, Vietnam, Yemen, Zambia and Zimbabwe.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get Pro in three steps
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Download Off Grid AI&lt;/strong&gt; for your computer or phone from the &lt;a href="https://getoffgridai.co/download/" rel="noopener noreferrer"&gt;download page&lt;/a&gt;. Chat works right away, free.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Open the &lt;a href="https://getoffgridai.co/pro/" rel="noopener noreferrer"&gt;Pro page&lt;/a&gt;&lt;/strong&gt; and check the price says $20 with your country's name. On your phone, tap &lt;strong&gt;Get Pro&lt;/strong&gt; in the app and the same checkout opens.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pay once.&lt;/strong&gt; Your key arrives by email. Enter it in the app and Pro starts straight away. Use the same key on your other devices.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsp5qeu8vcbuhlyct8exl.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsp5qeu8vcbuhlyct8exl.webp" alt="The Off Grid AI home screen on an iPhone, with local text, image, voice and speech models, a New Chat button, Clipboard and Sync devices cards and recent chats." width="640" height="1391"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The same key unlocks Pro on your phone. iPhone shown.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Fixing common problems
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you see&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;th&gt;What to do&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The page shows $34.99, not $20&lt;/td&gt;
&lt;td&gt;You're on a VPN or proxy, so the site sees a different country&lt;/td&gt;
&lt;td&gt;Turn the VPN off and reload the Pro page&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Your card is declined&lt;/td&gt;
&lt;td&gt;The charge is in US dollars, and some cards block payments to other countries&lt;/td&gt;
&lt;td&gt;Turn on international online payments for the card in your bank's app, or use another card&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No key in your inbox&lt;/td&gt;
&lt;td&gt;It went to the email you paid with&lt;/td&gt;
&lt;td&gt;Check spam and promotions for a message from Off Grid AI&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;How much is Off Grid AI Pro in India?&lt;/strong&gt;&lt;br&gt;
$20 once for lifetime access. The same price applies in 82 countries, including Brazil, Indonesia, Mexico, Nigeria, Pakistan, Bangladesh, the Philippines and Kenya. Checkout applies it from where you are, with no code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need a coupon or promo code?&lt;/strong&gt;&lt;br&gt;
No. Checkout sees which country you are paying from and charges $20. The Pro page and the bar at the top of the site show the same price before you start.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What do I get for $20?&lt;/strong&gt;&lt;br&gt;
Every Pro feature for life on up to 5 devices, desktop and phone: meeting notes without a bot, dictation, screen memory and search, Notes and Scribe, the password Vault, clipboard history and sync between your devices. Every update is included.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is the AI chat free?&lt;/strong&gt;&lt;br&gt;
Yes. Private chat with local models, image making, voice and reading your files are free on Mac, Windows, Linux, iPhone and Android, with no account. Pro adds the features that remember your work and act on it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why is the price lower in some countries?&lt;/strong&gt;&lt;br&gt;
A monthly AI bill priced in US dollars costs far more of a month's income in India or Nigeria than in the US. $20 once puts the same private AI within reach, and you never pay again.&lt;/p&gt;

&lt;h2&gt;
  
  
  Related guides
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://getoffgridai.co/articles/how-much-do-ai-subscriptions-cost-in-2026-yearly-totals-for-popular-ai-tools-and-what-paying-once-saves/" rel="noopener noreferrer"&gt;How much do AI subscriptions cost in 2026?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://getoffgridai.co/articles/which-ai-subscriptions-can-you-replace-with-one-app-in-2026-pay-once-runs-on-your-own-devices/" rel="noopener noreferrer"&gt;Which AI subscriptions can you replace with one app?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://getoffgridai.co/articles/how-to-sync-passwords-between-your-iphone-and-mac-in-2026-without-icloud-keychain-or-a-password-cloud/" rel="noopener noreferrer"&gt;How to sync passwords between your iPhone and Mac&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://getoffgridai.co/pro/" rel="noopener noreferrer"&gt;Get Off Grid AI Pro for $20&lt;/a&gt; and keep your AI, your notes and your passwords on your own devices.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>privacy</category>
      <category>productivity</category>
      <category>india</category>
    </item>
    <item>
      <title>The ethics of AI-assisted development</title>
      <dc:creator>Isabela Karkache</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:47:17 +0000</pubDate>
      <link>https://dev.to/icka/the-ethics-of-ai-assisted-development-4f66</link>
      <guid>https://dev.to/icka/the-ethics-of-ai-assisted-development-4f66</guid>
      <description>&lt;p&gt;Lately there's been a lot of discussion about the morality of creating software using artificial intelligence. I've noticed a growing wave of anti-AI sentiment particularly directed at independent developers, even those wh odon't use generative AI to create visual or audio assets, but rely on it solely as an assistant for writing code and documentation.&lt;/p&gt;

&lt;p&gt;I think there's a fundamental misunderstanding here that needs to be addressed; AI-assisted coding and generative AI "art" are two different things.&lt;/p&gt;

&lt;p&gt;Programming isn't an abstract form of creative expression in the same way visual art is. It's built on logic, mathematics, and problem solving, there are only so many ways to implement a particular funcionality. Sure, there can be countless variations in how code is written, structured and organized, but the underlying logic and possible solutions are constrained by the problem itself.&lt;/p&gt;

&lt;p&gt;It's simply not reasonable to accuse a developer of stealing another developer's work just because they used AI assistance to write a piece of code that happens to resemble something someone else has written. It's inevitable that developers will independently arrive at similar solutions, whether they use AI or not. &lt;em&gt;Of course, if the end result is an identical copy of someone else's software, then we're talking about plagiarism or outright theft of someone else's work, but that's an entirely different issue.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Now, looking at this from a broader socioeconomic perspective, AI is here to stay, it's not something we can realistically fight our way out of, and while the concerns behind the anti-AI movement are often legitimate, I think a lot of that criticism is being directed at the wrong target. Big tech companies and major game studios are actively embracing AI, yet they rarely seem to face the same level of public backlash, but when an independent developer releases a game and includes a disclaimer stating that they used AI to assist with coding, the reaction can be completely different; I've come across accounts on Reddit from indie developers who experienced waves of harassment and negative Steam reviews simply because they disclosed using AI for coding assistance.&lt;/p&gt;

&lt;p&gt;I'm not an unconditional supporter of AI. I understand the environmental concerns, especially the impact of data centers, their energy consumption, and the strain they put on water resources and local environments, these are real issues, and I don't think they should be dismissed. But I can't help seeing a parallel with the way environmental responsibility is often discussed. We're constantly told to be more conscious as individuals, to take shorter showers, consume less, and change our habits, while massive industries are allowed to keep exploiting natural resources in pursuit of ever-increasing profits.&lt;/p&gt;

&lt;p&gt;It's a contradiction and, in many ways, I think the anti-AI movement falls into a similar trap, focusing its anger on individuals and small developers instead of addressing the companies, economic structures, and business practices that are actually driving the larger problem.&lt;/p&gt;

&lt;p&gt;Anyway, this has been on my mind for a while, and I felt like putting my thoughts out there, so here's my take on it.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>ethics</category>
      <category>opensource</category>
    </item>
    <item>
      <title>How to Build a Career in Agentic AI: A Step-by-Step Roadmap for 2027</title>
      <dc:creator>Gowtham Sai Adavilayyagari</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:46:56 +0000</pubDate>
      <link>https://dev.to/gowtham_saiadavilayyagar/how-to-build-a-career-in-agentic-ai-a-step-by-step-roadmap-for-2027-3lfk</link>
      <guid>https://dev.to/gowtham_saiadavilayyagar/how-to-build-a-career-in-agentic-ai-a-step-by-step-roadmap-for-2027-3lfk</guid>
      <description>&lt;p&gt;Introduction&lt;br&gt;
&lt;a href="https://iabac.org/artificial-intelligence-certification/artificial-intelligence-foundation" rel="noopener noreferrer"&gt;Agentic AI&lt;/a&gt; systems can plan tasks, use approved tools, retrieve information and complete several steps with human oversight. Businesses are exploring them for customer support, research and internal operations, creating opportunities for people who can build and manage them.&lt;/p&gt;

&lt;p&gt;A career in this field requires strong foundations, practical projects and the ability to make systems safe and dependable. This guide outlines career options and a beginner-friendly roadmap for 2027.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Career Roles in &lt;a href="https://iabac.org/artificial-intelligence-certification/artificial-intelligence-foundation" rel="noopener noreferrer"&gt;Agentic AI&lt;/a&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;An agent combines a model, instructions, tools and data. A support agent, for example, could check an order, find a delivery policy and draft a response for human approval.&lt;/p&gt;

&lt;p&gt;Common career paths include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Agentic AI Engineer: Builds agents that plan tasks, use tools and manage multi-step workflows.&lt;/li&gt;
&lt;li&gt;Applied AI or LLM Engineer: Adds language-model features, retrieval and structured outputs to software products.&lt;/li&gt;
&lt;li&gt;AI Solutions Architect: Designs how models, data, applications, security and cloud services work together.&lt;/li&gt;
&lt;li&gt;AI Automation Developer: Connects agents to business applications and automates repeatable processes.&lt;/li&gt;
&lt;li&gt;AI Evaluation and Safety Specialist: Tests accuracy, prompt injection risks, tool permissions and harmful outputs.&lt;/li&gt;
&lt;li&gt;AI Product Manager or Consultant: Identifies business problems, defines success measures and coordinates delivery.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Choose a path that matches your strengths: developers may prefer engineering, data professionals retrieval and evaluation, and analysts workflow or product roles.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A Step-by-Step Roadmap for 2027&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Step 1: Build Your Technical Foundation&lt;/p&gt;

&lt;p&gt;Learn Python basics, APIs, JSON, error handling, Git and SQL. Study machine learning, large language models, tokens, context windows and model limitations.&lt;/p&gt;

&lt;p&gt;Milestone: Write a small Python program that sends a request to an LLM API and handles its response.&lt;/p&gt;

&lt;p&gt;Step 2: Understand How AI Agents Work&lt;/p&gt;

&lt;p&gt;Study an agent's goal, model, instructions, tools, state and feedback loop. Compare fixed workflows with agents that choose next steps. Start with one framework, validate tool inputs and restrict permissions.&lt;/p&gt;

&lt;p&gt;Milestone: Build a simple agent that calls one tool and explains what it did.&lt;/p&gt;

&lt;p&gt;Microsoft's &lt;a href="https://learn.microsoft.com/en-us/training/paths/build-foundation-extend-microsoft-365-copilot/" rel="noopener noreferrer"&gt;beginner learning path for building AI agents&lt;/a&gt; introduces agent components, use cases, tools, governance and solution planning. &lt;cite&gt;&lt;/cite&gt;&lt;/p&gt;

&lt;p&gt;Step 3: Learn RAG and System Integration&lt;/p&gt;

&lt;p&gt;Learn retrieval-augmented generation (RAG), document chunking, embeddings, semantic search and citations. Connect an agent to a database or test API, using authentication and least-privilege access.&lt;/p&gt;

&lt;p&gt;Step 4: Build Two or Three &lt;a href="https://iabac.org/blog/ai-projects-for-beginners" rel="noopener noreferrer"&gt;Practical Projects&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Build projects that solve clear problems: a document assistant, a research helper or a helpdesk agent that classifies tickets and drafts replies.&lt;/p&gt;

&lt;p&gt;Publish the code with a README covering the problem, design, setup, tests and limitations. A working project with honest evaluation is stronger evidence than a list of tools.&lt;/p&gt;

&lt;p&gt;Step 5: Test, Secure and Deploy&lt;/p&gt;

&lt;p&gt;Test answers and actions, including missing information and tool failures. Study prompt injection, privacy, monitoring and cost controls. Deploy a small project and document how to pause or roll it back.&lt;/p&gt;

&lt;p&gt;Step 6: Prepare for Job Applications&lt;/p&gt;

&lt;p&gt;Tailor your résumé to a target role. For each project, explain the problem, your contribution, tools, evaluation and improvements. Practise discussing design choices and seek internships, junior roles or workplace automation projects.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Skills Needed for Agentic AI and the&lt;a href="https://iabac.org/blog/future-of-certified-business-analytics-in-ai" rel="noopener noreferrer"&gt; Future&lt;/a&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Key technical skills include Python, APIs, SQL, Git, LLMs, RAG, orchestration, testing and cloud deployment. Build foundations before specialising.&lt;/p&gt;

&lt;p&gt;A useful way to practise is to take one ordinary task and map every step before choosing a tool. Identify the information needed, the decision points, the actions an agent may take and the points where a person must review the result. This habit prevents overengineering and makes your project easier to explain in interviews. Keep learning through documentation, small experiments and feedback from other developers. Tools will change, but the ability to define a problem, test a solution and explain its risks will remain valuable across roles and industries in real workplace settings.&lt;/p&gt;

&lt;p&gt;Analytical thinking, communication, curiosity and adaptability are equally important. The World Economic Forum's &lt;a href="https://www.weforum.org/publications/the-future-of-jobs-report-2025/" rel="noopener noreferrer"&gt;Future of Jobs Report 2025&lt;/a&gt; identifies AI and big data, technological literacy, analytical thinking and adaptability among skills expected to grow in importance through 2030. &lt;cite&gt;&lt;/cite&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Benefits and Practical Examples&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Agentic AI combines software, data, automation and business problem-solving. A retail agent might check stock, a logistics agent identify delayed shipments, and a research agent collect approved sources for review.&lt;/p&gt;

&lt;p&gt;Agents can misunderstand instructions or use incomplete information. Professionals must design clear limits and human review points.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Challenges and Limitations&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Job titles and employer expectations vary. A demo may fail with new data, while production systems need security reviews, reliable integrations and monitoring. Some tasks are better handled by a simple script or fixed workflow.&lt;/p&gt;

&lt;p&gt;Avoid collecting certificates without building practical ability. Be honest about what a project can do. Do not describe a system as fully autonomous if a person approves important actions.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;a href="https://iabac.org/blog/ai-engineer-salary-and-career-growth" rel="noopener noreferrer"&gt;Future Opportunities and Salary Ranges&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;AI opportunities may grow across software, consulting, finance, healthcare administration and manufacturing, but no one can guarantee the number of agentic AI jobs in 2027. Integration, evaluation and security skills may help candidates stand out.&lt;/p&gt;

&lt;p&gt;Salary varies by location, experience and employer. One recruiter estimate for India in 2027 puts fixed annual pay for agentic AI engineers at about ₹15–24 lakh at entry level, ₹28–50 lakh at mid level and ₹45–75 lakh at senior level. These are indicative figures, not guaranteed or standardised bands. Check current vacancies; beginners may enter through software, data or automation roles. &lt;cite&gt;&lt;/cite&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;IABAC Learning Resources&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A structured learning path can help identify gaps. The &lt;a href="https://iabac.org/artificial-intelligence-certification/certified-agentic-ai-professional" rel="noopener noreferrer"&gt;IABAC Certified Agentic AI Professional (CAAIP)&lt;/a&gt; covers agent foundations, LLM applications, RAG, orchestration, enterprise integration, evaluation, security and deployment. Review the syllabus and eligibility information to decide whether it matches your experience.&lt;/p&gt;

&lt;p&gt;You can also read IABAC's &lt;a href="https://iabac.org/blog/career-in-agentic-ai" rel="noopener noreferrer"&gt;career roadmap for agentic AI&lt;/a&gt; and explore the wider &lt;a href="https://iabac.org/certifications" rel="noopener noreferrer"&gt;IABAC certification catalogue&lt;/a&gt;. Certification can support structured learning, but it does not replace project experience or guarantee employment.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Frequently Asked Questions&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Do I need a computer science degree?&lt;/p&gt;

&lt;p&gt;Not always. Employers look for relevant skills and evidence of practical ability. A technical degree can help, but a strong portfolio and software foundations also matter.&lt;/p&gt;

&lt;p&gt;Is Python necessary?&lt;/p&gt;

&lt;p&gt;Python is a useful starting point because it is widely used for AI applications. Other languages may be relevant depending on the product and employer.&lt;/p&gt;

&lt;p&gt;How can a beginner gain experience?&lt;/p&gt;

&lt;p&gt;Start with a small RAG assistant or tool-using agent. Test it with different inputs, document its limitations and publish a clear project explanation.&lt;/p&gt;

&lt;p&gt;How long does it take to learn agentic AI?&lt;/p&gt;

&lt;p&gt;It depends on your starting point and study time. Someone with programming experience may build a basic project sooner than a complete beginner. Focus on milestones rather than a fixed promise.&lt;/p&gt;

&lt;p&gt;Does certification guarantee a job?&lt;/p&gt;

&lt;p&gt;No. Certification can demonstrate assessed knowledge, but hiring depends on skills, projects, experience and employer requirements.&lt;/p&gt;

&lt;p&gt;Conclusion&lt;/p&gt;

&lt;p&gt;Build your career step by step: learn programming and AI basics, understand tools and data, create projects, and practise evaluation, security and deployment. Focus your portfolio on real problems. Strong candidates will know how to make agents useful, safe and reliable.&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>career</category>
    </item>
    <item>
      <title>Let the LLM Read the Paperwork, Not Make the Decision</title>
      <dc:creator>Abivarma R S</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:46:39 +0000</pubDate>
      <link>https://dev.to/abivarma/let-the-llm-read-the-paperwork-not-make-the-decision-355j</link>
      <guid>https://dev.to/abivarma/let-the-llm-read-the-paperwork-not-make-the-decision-355j</guid>
      <description>&lt;p&gt;The common assumption is that an agent loop makes an existing decision smarter. For regulated eligibility checks on structured data, it mostly makes it more expensive, slower and harder to defend.&lt;/p&gt;

&lt;p&gt;Take a lender's debt-to-income check. The core is one line:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;eligible&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;debt&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="n"&gt;income&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&lt;/span&gt; &lt;span class="mf"&gt;0.43&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(43% is an example, not a regulatory figure.) The application is already typed: income, debts, loan amount from a form. Sometimes there's a handwritten hardship letter attached. The proposal on the table is to retire the rules engine and let an agent decide.&lt;/p&gt;

&lt;p&gt;I'd say no, and the reason isn't the token bill first. With illustrative numbers (250,000 decisions a month, 18,000 tokens per decision, $5 per million tokens) the agent costs $0.09 a decision and $22,500 a month to compute a ratio the rule already gets right. Latency goes from milliseconds to seconds because the calls run in sequence. But cost is the criterion I weigh last.&lt;/p&gt;

&lt;p&gt;What I weigh first is what an inconsistent answer costs. In lending, you have to show why someone was declined and that the same facts would produce the same decision again. A model predicts likely tokens. Most of the time it gets the arithmetic right. Give it income as "$115,000 / yr" and an ambiguous auto lease, and it can misread units, drop a digit or talk itself into an exemption that doesn't exist. The rule can't.&lt;/p&gt;

&lt;p&gt;The adaptability pitch is where I push back hardest. Change an if/else and your tests and CI tell you exactly what moved. Change an English prompt and you can fix rule A, silently break rule B, and not know which applicants were affected.&lt;/p&gt;

&lt;p&gt;So the design I'd pick keeps the rule at the core and gives the model one narrow job at the edge:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Before the model: input validation, PII scrubbing, and the rule checks that don't need the attachment.&lt;/li&gt;
&lt;li&gt;The model: one single-turn extraction of income, debts and a hardship reason from the letter.&lt;/li&gt;
&lt;li&gt;After the model: schema validation (a Pydantic model works), business-rule bounds and sanity checks. Anything that fails goes to a human queue. Only validated numbers reach the same DTI rule as everyone else.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Token spend then follows the paperwork that needs reading, not the number of applications.&lt;/p&gt;

&lt;p&gt;It's not free. A tested rules service takes weeks where a prompt takes an afternoon, someone has to staff the review queue, and deterministic code is consistently wrong if it encodes the wrong definition of income. Determinism makes errors reproducible. People still have to check the rule matches the policy.&lt;/p&gt;

&lt;p&gt;If you're looking at your own systems:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;If the logic can be written as rules and the input is structured, code decides. A model only reads the unstructured part.&lt;/li&gt;
&lt;li&gt;Make one standing rule in design review: no model output writes to a database or calls an external API without passing deterministic validation.&lt;/li&gt;
&lt;li&gt;If an agent already decides, run the rule in shadow mode on live traffic and understand every disagreement before you cut over.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The full article has the four options compared, the decision flow, the ownership split, the five-step migration and the sources: &lt;a href="https://pub.towardsai.net/let-the-llm-read-the-paperwork-not-make-the-decision-e52b71e22032" rel="noopener noreferrer"&gt;https://pub.towardsai.net/let-the-llm-read-the-paperwork-not-make-the-decision-e52b71e22032&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>architecture</category>
    </item>
    <item>
      <title>How to Automate a YouTube Channel with AI (Step-by-Step Guide)</title>
      <dc:creator>Saad Abusaad</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:46:12 +0000</pubDate>
      <link>https://dev.to/saad_abusaad_a3601876c923/how-to-automate-a-youtube-channel-with-ai-step-by-step-guide-2mp5</link>
      <guid>https://dev.to/saad_abusaad_a3601876c923/how-to-automate-a-youtube-channel-with-ai-step-by-step-guide-2mp5</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://aitoolsget.com/how-to-automate-youtube-channel-with-ai/" rel="noopener noreferrer"&gt;AIToolsGet&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Last updated:&lt;/strong&gt; 11 November 2026&lt;/p&gt;

&lt;p&gt;If you are wondering how to automate a YouTube channel with AI, the practical answer is this: let AI handle the slow, repeatable work (research, first drafts, voice-overs, rough edits, thumbnails and scheduling) and keep the parts that make a channel worth watching, your ideas, your fact-checking and your point of view, in your own hands. That split is what lets one person publish on a steady schedule without burning out, and it is also what keeps a channel on the right side of YouTube's rules.&lt;/p&gt;

&lt;p&gt;Below is a seven-step workflow with a free-to-start tool for each stage, a plain-English summary of the policies that matter, and the mistakes that most often hurt new channels. If you want a wider tool roundup first, start with our list of the &lt;a href="https://aitoolsget.com/ai-tools-for-youtube-automation/" rel="noopener noreferrer"&gt;best AI tools for YouTube automation&lt;/a&gt;, then come back here for the step-by-step process.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "Automating" a YouTube Channel Really Means
&lt;/h2&gt;

&lt;p&gt;Full automation, where software picks a topic, writes the script, voices it, edits it and uploads it without a person ever reviewing the result, is the exact pattern YouTube's monetization rules are written against. What works is partial automation. You build a repeatable pipeline, AI speeds up each stage, and you review what comes out before anything goes live.&lt;/p&gt;

&lt;p&gt;Here is a useful way to split the work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Good to automate:&lt;/strong&gt; topic research and keyword ideas, outlines and first-draft scripts, voice-overs, captions, rough cuts, thumbnail drafts and upload scheduling.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Keep human:&lt;/strong&gt; choosing the angle, fact-checking every claim, rewriting the script in your own voice, deciding what actually gets published, and anything that presents itself as expert health, legal, financial or political advice.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Automation saves time on each video. It does not replace having something to say.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick Picks: AI Tools for Each Step
&lt;/h2&gt;

&lt;p&gt;These are the tools used in this guide. Each one is a starting point rather than a requirement, and limits and prices change often, so check the official page before you rely on any of them.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Tool examples&lt;/th&gt;
&lt;th&gt;Free start?&lt;/th&gt;
&lt;th&gt;Watch out&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Research&lt;/td&gt;
&lt;td&gt;YouTube search, YouTube Studio analytics, vidIQ&lt;/td&gt;
&lt;td&gt;YouTube tools are free; vidIQ lists a free plan&lt;/td&gt;
&lt;td&gt;Keyword scores are estimates, not guarantees&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Script&lt;/td&gt;
&lt;td&gt;ChatGPT, Claude or Gemini&lt;/td&gt;
&lt;td&gt;Check each tool's current free access&lt;/td&gt;
&lt;td&gt;AI can state wrong facts confidently, so verify&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Voice-over&lt;/td&gt;
&lt;td&gt;ElevenLabs, CapCut text-to-speech&lt;/td&gt;
&lt;td&gt;Both offer a free option, with usage limits&lt;/td&gt;
&lt;td&gt;Read the free plan's terms on commercial use&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Visuals and editing&lt;/td&gt;
&lt;td&gt;CapCut&lt;/td&gt;
&lt;td&gt;Free to try online&lt;/td&gt;
&lt;td&gt;Pricing varies by region, device and promotion&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Thumbnails&lt;/td&gt;
&lt;td&gt;Canva&lt;/td&gt;
&lt;td&gt;Free plan available&lt;/td&gt;
&lt;td&gt;Premium assets need a paid plan&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Upload and schedule&lt;/td&gt;
&lt;td&gt;YouTube Studio&lt;/td&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;td&gt;Answer the AI disclosure question honestly&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Prices vary by region, billing period and device, and the price trackers we checked disagree with each other, so we have not printed exact numbers here. Verify the latest price on every official page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Choose a Niche and Research Topics
&lt;/h2&gt;

&lt;p&gt;Start with a niche where you can add something original: a clear explanation, a tested method, a useful comparison or a well-edited summary of research. Faceless channels work best when the value sits in the research and the explanation rather than in an on-camera personality. Tutorials, explainers and how-to series are common examples.&lt;/p&gt;

&lt;p&gt;Research comes next. Use YouTube's search suggestions, the most-viewed videos of channels in your niche and YouTube Studio's analytics to see what viewers already want. A keyword tool such as vidIQ, which lists a free plan, can add search-demand estimates, though those numbers are estimates and not promises.&lt;/p&gt;

&lt;p&gt;Then plan ahead. Ask your AI assistant for 20 topic ideas, cut the list to the 10 you can actually do well, and record each one in a simple sheet with the topic, the angle, the target viewer and the main keyword. A series is fine with YouTube as long as each video has its own focus, which the rules section below explains.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Write Scripts with AI, Then Make Them Yours
&lt;/h2&gt;

&lt;p&gt;An AI assistant such as ChatGPT, Claude or Gemini is good at structure. Give it your angle, your target viewer, the video length and the outline you want (a hook, three main points and a closing line), then ask for an outline first and a draft second. A prompt like this works well:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Act as a script editor for a YouTube channel about [niche]. The viewer is a beginner. Write an outline for a 6-minute video on [topic] with a 15-second hook, three main points with one example each, and a closing line. Do not invent statistics; mark anything that needs a source.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The draft is only the starting point. Check every fact against a reliable source, add an example or opinion that only you can give, and rewrite the lines until they sound like you. YouTube's own guidance lists using AI to edit video scripts as an acceptable use, and it treats outlines and scripts as minor production help that does not need an AI disclosure label.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Add an AI Voice-Over
&lt;/h2&gt;

&lt;p&gt;Text-to-speech tools turn the script into narration. ElevenLabs and CapCut both offer it. According to the price trackers we checked, ElevenLabs has a free plan, and CapCut lets you try its editor online for free. Free plans usually come with usage limits, so check how much audio you get and whether the free terms allow commercial use before you build a channel on them.&lt;/p&gt;

&lt;p&gt;Read the script aloud once before you generate the audio. Awkward sentences are easy to hear and easy to fix. Choose one consistent voice for the channel, adjust the pacing and add pauses where a point needs room to land.&lt;/p&gt;

&lt;p&gt;YouTube's help page lists cloning your own voice for voice-overs among the uses that need no AI disclosure. Making a real person appear to say or do something they did not do is different: that must be disclosed, and cloning someone else's voice raises consent and legal problems in the first place, so don't.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Build Visuals and Edit Faster
&lt;/h2&gt;

&lt;p&gt;CapCut is a common choice for assembling the video: cutting clips, adding captions and fitting everything to the voice-over. Your visuals can be screen recordings, your own charts and diagrams, licensed stock footage and, where it serves the story, AI-generated clips.&lt;/p&gt;

&lt;p&gt;This is the step where channels most often drift into trouble. YouTube's policy names image slideshows or scrolling text with little narrative or commentary as content that cannot be monetized, and it also lists videos that stitch together unrelated AI clips just to surprise viewers. Build each video around a clear beginning, middle and end, with visuals that support the explanation instead of decorating it.&lt;/p&gt;

&lt;p&gt;Use the free tier first. CapCut's help page says its pricing varies by region, device and promotions, so judge any paid plan against a limit you have actually hit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Create Thumbnails and Titles
&lt;/h2&gt;

&lt;p&gt;Canva has a free plan, which is enough to design thumbnails. Set up one template for your brand colours and fonts, then change the image and the words for every video so each thumbnail matches its own topic. Keep it to one idea and three to five words.&lt;/p&gt;

&lt;p&gt;Ask your AI assistant for ten title options, then choose the one that uses the phrase a viewer would really search for and promises only what the video delivers. Misleading packaging costs trust, and YouTube's policy also names deceptive imagery, such as realistic visuals that trick viewers into believing something false happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Upload, Schedule and Disclose
&lt;/h2&gt;

&lt;p&gt;YouTube Studio lets you schedule each upload for a specific date and time, so you can edit several videos in one sitting and let them publish across the week. Write a clear title, a description that explains the video in your own words, and chapters where they help.&lt;/p&gt;

&lt;p&gt;Check the AI disclosure question during upload. YouTube requires a label when content is realistic and was generated or meaningfully altered with AI, for example a realistic scene that never happened or a real person made to appear to say something they did not. Production help such as outlines, scripts, thumbnails, captions and audio repair does not need one. Answer honestly: YouTube says a disclosure on its own does not limit a video's audience or affect monetization eligibility, while consistently not disclosing can lead to a label added for you or to penalties, including suspension from the YouTube Partner Program.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Review Analytics and Improve
&lt;/h2&gt;

&lt;p&gt;Once a week, open YouTube Studio and look at click-through rate, average view duration and the audience retention graph for each new video. Retention dips show where viewers lose interest, which usually means a slow intro or a section that ran too long. You can paste your notes into an AI assistant and ask for ideas for the next hook, but let the numbers decide, not the assistant's guess.&lt;/p&gt;

&lt;p&gt;Then repeat the loop: research, script, voice, edit, thumbnail, upload, review. The pipeline gets faster because you improve it every round, not because the AI does more of the thinking.&lt;/p&gt;

&lt;h2&gt;
  
  
  YouTube Rules You Must Follow When You Automate
&lt;/h2&gt;

&lt;p&gt;YouTube's channel monetization policies say your content should be your original creation, and should not be mass-produced, generic, repetitive or manipulative. Reviewers look at a channel's main theme, most viewed videos, newest videos and metadata such as titles, thumbnails and descriptions. The policy page currently groups the relevant rules into three categories under inauthentic content:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Generic or repetitive content:&lt;/strong&gt; videos that look made from a template or feel interchangeable, with little educational value, commentary or variation.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Unsatisfying or off-putting content:&lt;/strong&gt; emotionally manipulative formulas, interchangeable copies of existing formats, or shock content with no real narrative.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;AI personas on sensitive topics:&lt;/strong&gt; channels that present an AI-generated character as a human expert giving health, legal, financial or political advice cannot monetize.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What is fine: using the same intro and outro, running a series where each video has its own focus, and using AI tools to help deliver a unique, well-researched narrative. The test is whether each video gives viewers something real that your other videos do not.&lt;/p&gt;

&lt;p&gt;One caution about timing. Tubefilter reported in July 2026 that YouTube reworded this guidance and described the change as a clearer explanation rather than new rules, while the changelog note we saw on the policy page itself still showed the 2025 entry. Policies shift, so read the live page before you commit to a workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Mistakes to Avoid
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Publishing raw AI output without a fact-check or a rewrite.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Using one template for every video with only the topic swapped.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Skipping disclosure on realistic AI visuals or voices.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Building an AI "expert" who gives health, money or legal advice.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Uploading daily for the sake of volume, which makes quality drop.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Ignoring a tool's licence terms before using its output commercially.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A Simple Weekly Workflow
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Day&lt;/th&gt;
&lt;th&gt;Task&lt;/th&gt;
&lt;th&gt;Where AI helps&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Monday&lt;/td&gt;
&lt;td&gt;Pick topics and keywords&lt;/td&gt;
&lt;td&gt;Brainstorming and title ideas&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tuesday&lt;/td&gt;
&lt;td&gt;Write scripts&lt;/td&gt;
&lt;td&gt;Outline and first draft&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Wednesday&lt;/td&gt;
&lt;td&gt;Voice-over and visuals&lt;/td&gt;
&lt;td&gt;Text-to-speech and asset ideas&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Thursday&lt;/td&gt;
&lt;td&gt;Edit and make thumbnails&lt;/td&gt;
&lt;td&gt;Captions, rough cuts, thumbnail drafts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Friday&lt;/td&gt;
&lt;td&gt;Upload and schedule&lt;/td&gt;
&lt;td&gt;Description and chapter drafts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Weekend&lt;/td&gt;
&lt;td&gt;Review analytics&lt;/td&gt;
&lt;td&gt;Summarising patterns in your notes&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can you fully automate a YouTube channel with AI?
&lt;/h3&gt;

&lt;p&gt;You can connect tools into a pipeline, but a channel with no human review is the pattern YouTube's rules target, and it is rarely good enough to keep viewers. Partial automation with human review is the safer and better approach.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can AI-generated videos earn money on YouTube?
&lt;/h3&gt;

&lt;p&gt;Using AI is not banned. YouTube's examples of acceptable use include using AI to edit scripts or to generate a unique background visual, as long as the video shows your own creative direction and gives viewers value. Generic, repetitive or mass-produced content is not eligible.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I have to label my video as AI-generated?
&lt;/h3&gt;

&lt;p&gt;Only when it is realistic content that was generated or meaningfully altered with AI. Outlines, scripts, thumbnails, captions and audio repair are listed as not needing a label. Check YouTube's help page for the current list.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the cheapest way to start?
&lt;/h3&gt;

&lt;p&gt;Begin with the free options in this guide, publish a few videos, and upgrade only when a specific limit blocks you. Read each tool's terms to see what its free plan allows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Automating a YouTube channel with AI is really about building a repeatable system and keeping yourself in the loop. Work through the seven steps, publish your first few videos on free options, and see what your analytics say before you spend anything. Whatever you build, keep one rule in front of you: every video should give viewers something they could not get from a generic template.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;p&gt;Prices and plans were checked on 11 November 2026 and may change.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://support.google.com/youtube/answer/1311392" rel="noopener noreferrer"&gt;YouTube Help, YouTube channel monetization policies&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://support.google.com/youtube/answer/14328491" rel="noopener noreferrer"&gt;YouTube Help, Disclosing use of GenAI content&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://www.tubefilter.com/2026/07/13/youtube-inauthentic-content-monetization-policy-update/" rel="noopener noreferrer"&gt;Tubefilter, report on YouTube's inauthentic content guidance (13 July 2026)&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://vidiq.com/pricing" rel="noopener noreferrer"&gt;vidIQ, pricing and plans&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://www.canva.com/en_en/pricing/" rel="noopener noreferrer"&gt;Canva, pricing&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://www.capcut.com/help/how-much-does-capcut-pro-cost" rel="noopener noreferrer"&gt;CapCut Help, How much does CapCut Pro cost&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://dupple.com/pricing/elevenlabs" rel="noopener noreferrer"&gt;Dupple, ElevenLabs pricing tracker (October 2026, third-party)&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>contentcreation</category>
      <category>ai</category>
      <category>automation</category>
      <category>youtube</category>
    </item>
    <item>
      <title>How to make ChatGPT and Claude write like a human (8 habits that actually work)</title>
      <dc:creator>Andrew</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:45:45 +0000</pubDate>
      <link>https://dev.to/andrew517/how-to-make-chatgpt-and-claude-write-like-a-human-8-habits-that-actually-work-274k</link>
      <guid>https://dev.to/andrew517/how-to-make-chatgpt-and-claude-write-like-a-human-8-habits-that-actually-work-274k</guid>
      <description>&lt;p&gt;Ask ChatGPT or Claude for a blog post and most of the time you can spot it right away. Two sentences in, it's obvious: a grand claim about how quickly everything is changing, paragraphs that all hit the same length, three bullet points when one would be plenty, and a tidy outro nobody asked for. Sure, the info checks out. It just doesn't sound like anyone you'd actually meet.&lt;/p&gt;

&lt;p&gt;I use AI assistants for writing all the time, and over the past year I've picked up a few habits that fix most of this. They're simple, and you don't need any special tools, except for one at the end. Here's what I do.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Show it how you write
&lt;/h2&gt;

&lt;p&gt;The quickest fix? Feed the model a chunk of your own writing. A couple of paragraphs from an old email, a LinkedIn post, whatever sounds like you. Then ask it to match that style. Models copy a voice pretty well when they have something real to work with. If you just say "write casually", you get a bland, generic version of casual. Drop in your actual words and the voice starts to feel like yours.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Ban the usual suspects
&lt;/h2&gt;

&lt;p&gt;Every model leans on favorite phrases and moves. Tell it up front what you don't want. My list: no "delve", "crucial", "seamless", "landscape", "in today's fast paced world", no "it's not just X, it's Y", no rhetorical questions as openers, no summary at the end.&lt;/p&gt;

&lt;p&gt;You can save this list as custom instructions in ChatGPT or as a project instruction in Claude, so you don't paste it every single time.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Ask for specifics, not summaries
&lt;/h2&gt;

&lt;p&gt;AI writing falls flat when it stays general. Hand over the details only you know: a number from your own data, a real client story (scrubbed for privacy), a mistake you actually made, the exact tool you used. Then tell the model to build the paragraph around that detail. One real example beats five paragraphs of advice.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Break the rhythm
&lt;/h2&gt;

&lt;p&gt;AI has a thing for sentences of the same length and neat little lists of three. Ask for something different:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Mix very short sentences with longer ones. Don't group things in threes. Some paragraphs can be one line.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then check the output. If every paragraph still has the same shape, call it out and have it try again.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Cut the intro and the outro
&lt;/h2&gt;

&lt;p&gt;Almost every AI draft starts with a warm up paragraph and closes with "In conclusion" or "By following these tips". Chop both. Start with the first useful line and stop once the point lands. You can also spell it out:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Start with the main point. No introduction, no conclusion paragraph.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  6. Edit in a conversation, not in one prompt
&lt;/h2&gt;

&lt;p&gt;That giant prompt you paste in? It rarely gets you a good draft. Ask for an outline first, fix it, then go section by section. After each part, tell the model exactly what bugged you: too stiff, too long, that line sounds like a sales pitch. A quick, specific complaint works way better than rewriting the whole prompt from scratch.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Run the draft through a humanizer without leaving the chat
&lt;/h2&gt;

&lt;p&gt;Even with solid prompts, long drafts slide back into the same habits. Sentences start to sound alike, transitions blur together, everything settles into that familiar pattern. For the final pass I use &lt;a href="https://humantone.io/" rel="noopener noreferrer"&gt;HumanTone&lt;/a&gt;, an AI humanizer that reworks sentence rhythm and structure but leaves the meaning alone. It connects to Claude and ChatGPT as an MCP tool, so the assistant calls it right inside the chat. No more bouncing text between tabs.&lt;/p&gt;

&lt;p&gt;Setup takes about a minute. The server URL is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://mcp.humantone.io/mcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In Claude, open Settings, then Connectors, add a custom connector with that URL and sign in. In ChatGPT, go to Plugins, add a custom MCP server with the same URL and pick OAuth.&lt;/p&gt;

&lt;p&gt;After that, name the tool in your prompt:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Use humantone to rewrite this draft:

[paste your text]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you skip the name, the assistant usually rewrites the text itself, and you end up with the same vibe you were trying to fix. You can also ask it for an AI likelihood score from 0 to 100. That's handy for finding the one paragraph that still reads like a template.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Read it out loud
&lt;/h2&gt;

&lt;p&gt;Old school, but it works. Read the final text out loud. If you hit a sentence you'd never say to a real person at work, rewrite it. Add one small detail that's actually yours, fix anything that's slightly off, and it reads like your writing again.&lt;/p&gt;

&lt;p&gt;That's my whole process. What do you do to make AI drafts sound like your own? I'm always curious what tricks other people have figured out.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>writing</category>
      <category>productivity</category>
      <category>chatgpt</category>
    </item>
  </channel>
</rss>
