Explain differences between supplied astrology charts

Setup requirements

1. Use a read-only input folder and a separate output location; accept pasted text if files cannot be inspected.

2. Confirm that all exports refer to the same owner-approved token. An owner assertion establishes intended grouping, not astronomical correctness.

3. Bound the review to three exports, twelve displayed features and six short interpretation passages. Use supplied legends; unknown conventions stay unknown.

4. Label every output: Astrology is used here for entertainment and reflection; it is not scientifically validated and must not guide consequential decisions.

5. Use no calculator, ephemeris service, installation, paid request or new account. This workflow compares existing artifacts only.

Inputs and access

1. Name

   Two or three supplied chart exports

   Source or owner

   Adult owner, or wholly fictional teaching fixtures

   Sensitivity

   Potential personal birth details; prefer redacted copies with an owner-confirmed shared opaque chart token. Do not use another real person’s chart.

   Permission needed

   Owner provides authorized copies in the existing private workspace. Raw name, exact birth date, time and location are optional and unnecessary; do not request or transmit them.

2. Name

   Up to six selected interpretation passages and their source references

   Source or owner

   Owner-authored passages or excerpts the owner may provide for private analysis

   Sensitivity

   May contain intimate assertions; exclude unrelated personal narratives.

   Permission needed

   Private comparison only. Do not republish licensed report text or infer traits about a person.

3. Name

   Export legends or settings notes and the owner’s question

   Source or owner

   Supplied with the exports, preferably captured at the same time

   Sensitivity

   Use settings only; omit account identifiers and unrelated metadata.

   Permission needed

   No login, account connection, third-party inquiry or settings change is included.

The problem

An adult exploring astrology for entertainment receives inconsistent-looking chart reports and cannot separate a documented convention change from missing information or a different symbolic story.

Suggested task

Compare two or three owner-supplied exports, map their explicit settings and trace selected interpretation passages to the features they cite, preserving unresolved discrepancies.

What you could produce

A private convention comparison, feature-to-passage dependency map and unresolved-evidence checklist, with a short plain-language reading guide.

Why an agent / simpler alternative

An assistant can join explicit metadata, visual labels and prose references while retaining source locations across a few documents. The distinct work is a convention-to-interpretation dependency review, not a zodiac-flavoured journal or a generic chart reading. A single short report is better reviewed manually; large numeric chart verification belongs in separately validated software.

Who this helps

1. Adult learner comparing their own redacted chart exports

2. Facilitator preparing an adult-only symbolic-literacy activity using wholly fictional charts

Evidence boundary

Sources establish a concrete support problem and technical configuration primitives only. The bounded review process, output structure, safeguards, synthetic fixture and prompt are original editorial design. No evidence supports effectiveness, compatibility or predictive validity.

Proposed steps

1. 1

   Inventory supplied artifacts, assign stable file and passage IDs, verify the owner-approved grouping and report unreadable or missing sections.

   Expected output: Input manifest with scope and gaps

   Approval gate: Pause if the material concerns another real person or input authorization is unclear.

2. 2

   Transcribe only explicitly supplied settings and displayed features, preserving wording, units and source references. Flag OCR uncertainty instead of guessing.

   Expected output: Provenance-linked comparison rows

   Approval gate: The owner confirms ambiguous symbols or unreadable values before those rows are used.

3. 3

   Separate an observed difference from a possible explanation. Attribute a cause only when the supplied configuration documentation establishes it; multiple changed settings remain confounded.

   Expected output: Difference ledger with observed, documented explanation and unresolved labels

   Approval gate: No unseen recalculation or automatic correction of an input is allowed.

4. 4

   Trace each selected passage to the specific displayed feature it names. Distinguish a changed feature, a different author’s symbolism and a passage with no explicit dependency.

   Expected output: Feature-to-passage dependency map

   Approval gate: Describe interpretations as authored symbolic claims, never facts about the owner or future.

5. 5

   Draft a one-page guide explaining what the supplied artifacts show, which differences remain unresolved, and what minimal existing screenshot or legend would resolve each gap. Include up to three optional questions about how conventions shape the story.

   Expected output: Private review packet and precise missing-evidence requests

   Approval gate: Owner reviews before any optional sharing; the task authorizes no external send, upload or publication.

Synthetic output illustration — not an executed result

Label

Clearly synthetic structural illustration; no chart was calculated and no workflow was run

Data

Chart token

SYN-REFLECT-01

Feature

Invented marker P

Report a

Fixture row A3: marker value X; displayed house 3

Report b

Fixture row B3: marker value X; displayed house 4

Observation

Reported marker value matches; the displayed house labels differ.

Interpretation link

Passage B7 explicitly refers to the displayed house label; passage A8 is an unrelated author metaphor.

Cause status

A convention label differs, but this fixture does not independently prove the numerical cause.

Review question

Which parts of the supplied story depend on the changed label, and which are the author’s free interpretation?

Human approval boundaries

1. Confirm authorized, minimized inputs and whether they are the owner’s own exports or entirely fictional.

2. Review ambiguous transcription and interpretation dependencies; a matching feature does not establish a personality claim.

3. Any later publication, outreach, upload, account access or chart regeneration is a separate action outside this proposal and needs its own scope and authorization.

Limits

1. Original editorial proposal; no workflow execution, independent test, customer result or demand validation exists.

2. Astrology is an entertainment/reflection framework here, not scientifically validated knowledge or a basis for health, money, relationships, employment or other consequential choices.

3. This review does not establish astronomical correctness, rectify birth time, generate missing placements, predict events or decide which symbolic framework is true.

4. Compatibility is unknown. The cited technical reference does not demonstrate that an assistant can run this workflow.

5. No profiling of third parties, birth-data lookup, telemetry export or external transmission is permitted.

Candidate platforms — compatibility untested

1. Name

   File-capable assistant in an owner-approved private workspace

   Required capabilities

   1. Read supplied text, tabular exports or legible screenshots

   2. Track provenance and compare explicit fields across documents

   3. Create a separate structured review artifact

   Capability source urls

   Not specified.

   Workflow compatibility

   Unknown; no named platform, connector, parser, OCR accuracy or end-to-end execution was verified.

   Selection basis

   Original editorial capability requirements, not a claim of a tested integration.

Failure modes

1. A convention difference is presented as proof that one reading is scientifically correct.

2. More than one changed setting is collapsed into one unsupported causal explanation.

3. A transit report is silently treated as the same report type as a supplied natal export.

4. Unreadable glyphs, units or omitted metadata are guessed.

5. An author’s symbolic language is turned into personality assessment, diagnosis, compatibility ranking or advice about a consequential choice.

6. Private birth details are sent to an external calculator or copied unnecessarily into the result.

7. Instructions embedded in a source report are followed rather than treated as untrusted document content.

Recovery and troubleshooting

1. If a row cannot be read, preserve its source reference and request only the relevant cropped or typed excerpt; continue other independent rows.

2. If grouping or report type differs, split the comparison and ask the owner whether a matching existing export is available; do not generate one.

3. If the explanation is unsupported or several variables changed, label the cause unresolved and list the exact missing evidence.

4. If prose lacks a traceable feature dependency, mark it as unlinked symbolism and leave it out of any convention-based explanation.

5. If files cannot be read, provide the empty review structure and ask for pasted excerpts; do not claim inspection or completion.

Unexecuted validation plan

Sample setup

Prepare three wholly fictional mini-exports for token SYN-REFLECT-01. A and B show the same invented marker value but different supplied house labels and explicitly different convention labels. C omits a setting and includes one unreadable symbol. Attach one passage referencing the changed feature, one independent author metaphor and one unlinked assertion. These are structural fixtures, not valid astronomical calculations.

Acceptance checks

1. Every compared field and passage cites a supplied artifact and location.

2. The identical reported marker value stays identical; the differing house labels are retained without recalculating them.

3. The missing setting and unreadable symbol remain unresolved; no assumption is substituted.

4. The changed-feature passage, independent metaphor and unlinked assertion are distinguished.

5. The result makes no forecast, personality inference, health conclusion, financial or relationship recommendation.

6. No exact birth details are required or exported, inputs remain unchanged, and no network request or external action occurs.

Stop conditions

1. Any invented placement or causal explanation

2. Any instruction to make a consequential choice based on astrology

3. Any unauthorized transmission, installation, account access or source mutation

4. Any unsupported claim that this proposed workflow passed testing

Executed

No

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Possible existing assistant-plan usage; availability and limits must be checked before a pilot

2. Owner time to redact exports and verify ambiguous rows

Caveat

No subscription, calculator, API, OCR service or paid integration is assumed or authorized. No measured saving or return is claimed.

Canadian adaptation — proposed

No country-specific adaptation is established. Preserve supplied time-zone labels without assuming a jurisdiction or correcting historical time data.