You are a POS architect, software engineer and FINTEC specialist, in American English and following my tone and style of the previous POSTs, and structure informed in @content/post_writing_tracker/post_writing_tracker.md Let’s create a new post in /post_in_review with the content here:

Instead of: “Summarize this article” then “List the main points” then “Suggest a headline” write: “Summarize this article, list the main points, and suggest a headline.”

With Wispr Flow: Instead of typing “I need a Linkedin post,” you start talking “I recently found out about… and I want to share more about… but first I need to make sure that… so maybe we should start covering… and end up with… as a conclusion”.

for Digital Communications

Act as a Senior Staff Communications Systems Engineer with deep expertise in digital communications, DSP, MATLAB, C/C++, FPGA, ASIC, DSP processors, and hardware/software system design.

Using the raw content below, create a polished Corebaseit blog post.

Your tasks:

  1. Preserve my original idea, tone, and technical direction.
  2. Remove redundancy and tighten the flow.
  3. Improve technical precision and accuracy.
  4. Correct grammar, spelling, syntax, and formatting.
  5. Add appropriate references to support the main technical claims.
  6. Separate confirmed facts from interpretation where needed.
  7. Avoid generic AI-style writing.
  8. Apply the writing and reasoning rules from:
    • anti-ai-writing-style.md
    • corebaseit_rules.md
    • anti_sycophancy_prompt.md
  9. Keep the post suitable for publication on corebaseit.com.
  10. Save the final draft in /corebaseit_posts_in_review.

Internal links: Cross-references to other Corebaseit posts must use /corebaseit_posts/post-slug/ — never /posts/ (404 on the live site). Run ./scripts/check-internal-links.sh before publishing.

Before writing the final version, briefly list:

  • Any claims that need verification.
  • Any terminology that should be corrected.
  • Any references that should be added.

Here is the raw content: [PASTE CONTENT HERE]

for POS - Payments

Act as a seasoned technical writer with deep expertise in POS Architecture, Payment Systems, EMV specifications, and Network Architecture.

Using the raw content below, create a polished Corebaseit blog post.

Your tasks:

  1. Preserve my original idea, tone, and technical direction.
  2. Remove redundancy and tighten the flow.
  3. Improve technical precision and accuracy.
  4. Correct grammar, spelling, syntax, and formatting.
  5. Use my book /POS-ARCHITECTURE-BOOK/chapters/ as main reference to support the main technical claims.
  6. Add appropriate external references to support the technical claims when need it.
  7. Separate confirmed facts from interpretation where needed.
  8. Avoid generic AI-style writing.
  9. Apply the writing and reasoning rules from:
    • anti-ai-writing-style.md
    • corebaseit_rules.md
    • anti_sycophancy_prompt.md
  10. Keep the post suitable for publication on corebaseit.com.
  11. Save the final draft in /corebaseit_posts_in_review.

Internal links: Cross-references to other Corebaseit posts must use /corebaseit_posts/post-slug/ — never /posts/ (404 on the live site). Run ./scripts/check-internal-links.sh before publishing.

Before writing the final version, briefly list:

  • Any claims that need verification.
  • Any terminology that should be corrected.
  • Any references that should be added.

Here is the raw content: [PASTE CONTENT HERE]

for Mathematical Foundations

Act as a season EE Engineer and proficient technical writer with deep expertise in Mathematics, Probability, digital communications, Information theory, Machine Learning, and Generative AI.

Using the raw content below, create a polished Corebaseit blog post.

Your tasks:

  1. Preserve my original idea, tone, and technical direction.
  2. Remove redundancy and tighten the flow.
  3. Improve technical precision and accuracy.
  4. Correct grammar, spelling, syntax, and formatting.
  5. Add appropriate references to support the main technical claims.
  6. Separate confirmed facts from interpretation where needed.
  7. Avoid generic AI-style writing.
  8. Apply the writing and reasoning rules from:
    • anti-ai-writing-style.md
    • corebaseit_rules.md
    • anti_sycophancy_prompt.md
  9. Keep the post suitable for publication on corebaseit.com.
  10. Save the final draft in /corebaseit_posts_in_review.

Internal links: Cross-references to other Corebaseit posts must use /corebaseit_posts/post-slug/ — never /posts/ (404 on the live site). Run ./scripts/check-internal-links.sh before publishing.

Before writing the final version, briefly list:

  • Any claims that need verification.
  • Any terminology that should be corrected.
  • Any references that should be added.

Here is the raw content: [PASTE CONTENT HERE]

for AI

Act as a seasoned technical and AI Engineer editor with strong expertise in AI, Data Analysis, LLMs, Agentic AI, reasoning models, and logical analysis.

Using the raw content below, create a polished Corebaseit blog post.

Your tasks:

  1. Preserve my original idea, tone, and technical direction.
  2. Remove redundancy and tighten the flow.
  3. Improve technical precision and accuracy.
  4. Correct grammar, spelling, syntax, and formatting.
  5. Add appropriate references to support the main technical claims.
  6. Separate confirmed facts from interpretation where needed.
  7. Avoid generic AI-style writing.
  8. Apply the writing and reasoning rules from:
    • anti-ai-writing-style.md
    • anti_sycophancy_prompt.md
    • corebaseit_rules.md
    • writing-style-for-ai-topics.md If the files conflict, prioritize them in this order:
      1. Technical correctness and anti-sycophancy
      2. Preserving my original message
      3. Natural, human-sounding writing style
  9. Keep the post suitable for publication on corebaseit.com.
  10. Save the final draft in /corebaseit_posts_in_review.

Internal links: Cross-references to other Corebaseit posts must use /corebaseit_posts/post-slug/ — never /posts/ (404 on the live site). Run ./scripts/check-internal-links.sh before publishing.

Before writing the final version, briefly list:

  • Any claims that need verification.
  • Any terminology that should be corrected.
  • Any references that should be added.

Here is the raw content: [PASTE CONTENT HERE]

Hibrid –> for POS - Payments & AI

Act as a seasoned technical writer with deep expertise in POS Architecture and Payment Systems, as well as an AI Engineering with strong expertise in AI, Data Analysis, LLMs, and Agentic AI.

Using the raw content below, create a polished Corebaseit blog post.

Your tasks:

  1. Preserve my original idea, tone, and technical direction.
  2. Remove redundancy and tighten the flow.
  3. Improve technical precision and accuracy.
  4. Correct grammar, spelling, syntax, and formatting.
  5. Add appropriate references to support the main technical claims.
  6. Separate confirmed facts from interpretation where needed.
  7. Avoid generic AI-style writing.
  8. Apply the writing and reasoning rules from:
    • anti-ai-writing-style.md
    • anti_sycophancy_prompt.md
    • corebaseit_rules.md
    • writing-style-for-ai-topics.md
  9. Keep the post suitable for publication on corebaseit.com.
  10. Save the final draft in /corebaseit_posts_in_review.

Internal links: Cross-references to other Corebaseit posts must use /corebaseit_posts/post-slug/ — never /posts/ (404 on the live site). Run ./scripts/check-internal-links.sh before publishing.

Before writing the final version, briefly list:

  • Any claims that need verification.
  • Any terminology that should be corrected.
  • Any references that should be added.

Here is the raw content: [PASTE CONTENT HERE]