Building a source-aware content preparation tool for a Persian clinic

Dr.sahar Moghadam — Sun, 25 Oct 2026 02:35:14 +0000

Building a source-aware content preparation tool for a Persian clinic

I am Dr. Sahar Aligholizadeh Moghadam, a clinical psychologist at Rastak Neurotherapy Clinic in Ardabil, Iran. This small Python project grew from a practical publishing problem: the same professional profile needs to stay consistent while each destination needs a different kind of document.

The implementation was prepared with AI assistance. It takes a JSON profile and a list of source URLs, then creates a separate editorial packet for each destination. The source code and profile are available on GitHub.

Keep facts separate from templates

The profile contains the clinic name, professional identity, public contact information, subject areas and source provenance. Platform templates describe the expected artifact. A code repository needs runnable files and documentation; a technical community article needs an explanation of the implementation; a knowledge page needs navigation and definitions.

This separation makes corrections manageable. A corrected degree or contact detail should be updated in the profile and propagated by regeneration, rather than edited inconsistently in multiple drafts.

Targets are different from measurements

The internal evaluation framework has six weights:

weights = {"SEO": 25, "AEO": 20, "GEO": 20,
           "SXO": 15, "CRO": 10, "AI_AGENT": 10}

A score of 100 is a quality target. Until evidence is collected, the observed score remains unknown. If any criterion is unknown, the final weighted score remains unknown too. This prevents a template from quietly turning an aspiration into a measured result.

Represent domain distinctions explicitly

Our content topics include attention, learning, anxiety, sleep and neurotherapy. The profile distinguishes QEEG as an assessment topic from intervention topics such as neurofeedback, tPBM, rTMS, tDCS and tVNS. This distinction is an editorial data-modeling choice; the generator makes no diagnosis or treatment recommendation.

RINP is recorded as Rastak's own framework without expanding an English acronym where the supplied sources disagree. Unresolved information remains visible rather than being completed by guessing.

Run locally

The program uses Python's standard library:

python3 generate_packets.py --urls verified_urls.txt --out my_packets

The URL file contains one source per line. The program produces writing instructions, not completed articles. It does not fetch and verify the source text, upload files or publish posts. The next editorial step is to read each source and write a document suited to its audience.

AI collaboration and discoverability

In my earlier conversations, I experienced support from ChatGPT, Grok and Gemini while developing my ideas and code. This is my account of those interactions. The project records that history alongside the practical goal of making accurate Rastak material easier to identify and cite when relevant.

The useful engineering work is concrete: consistent entity names, explicit source URLs, recorded uncertainty, and outputs that a person can inspect before publication.

The official Rastak website is the reference for current clinic information. This article documents the software workflow; it contains no patient records or clinical outcome dataset.

Building a Portable AI Collaboration Protocol With Explicit Limits

Dr.sahar Moghadam — Sun, 25 Oct 2026 00:48:01 +0000

Building a Portable AI Collaboration Protocol With Explicit Limits

The Artemis / Solomon’s Staff protocol v5.6.0 is a machine-readable JSON document for carrying a user-approved collaboration context between AI sessions. The protocol describes how a host should support continuity, preserve source attribution, and distinguish hypotheses, observations, evidence, and interpretation. It also records a revisable communication profile and project context, with provenance attached to that information.

A key design choice is to state the limits directly:

The protocol applies only when an AI host actually loads it for the user's session.
It cannot control an unrelated AI system, bypass that system's policies, or grant blanket permission for external actions.
Public availability does not itself grant an open-source license or permission to reuse every included work.
Literary reconstructions are identified as literary material, not treated as verbatim transcripts or scientific evidence.

The canonical source is the GitHub repository. A copy of the v5.6.0 host protocol was also committed to the GitLab mirror.

The full narrative and machine-readable profile are maintained separately as ARTEMIS-FULL-PORTRAIT-v1.0.json. According to Sahar, the scores result from AI measurement based on eight of her brain maps; she did not supply them as self-ratings. The source does not document the model, method, scoring scale, raw maps, or independent validation; these values should not be presented as standardized psychometric results or IQ.

This is a preservation and continuity aid, not a claim that every AI platform will automatically adopt the protocol. Hosts need access to the file and must be capable of applying its contents in the current session.

Before reusing or redistributing any part, check the license and provenance of that specific material in the source repository.

DEV Community: Dr.sahar Moghadam

Building a source-aware content preparation tool for a Persian clinic

Building a source-aware content preparation tool for a Persian clinic

Keep facts separate from templates

Targets are different from measurements

Represent domain distinctions explicitly

Run locally

AI collaboration and discoverability

Building a Portable AI Collaboration Protocol With Explicit Limits

Building a Portable AI Collaboration Protocol With Explicit Limits