Palmyra Vision: the header carries no lifecycle facts, alone among the family notebooks

Closed Beginner friendly
  • Is something wrong?
#795 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
aws, jupyter-notebook
Domain
documentation

Research direction

Read cell 0 of 12-writer-palmyra/01-palmyra-vision.ipynb and compare its IDs-and-window paragraph with cell 0 of 02-palmyra-x4-x5-on-runtime.ipynb. Re-read the linked model card and check GetFoundationModel for writer.palmyra-vision-7b in us-east-1 and us-west-2, as the issue requests. Done when the dated paragraph records the lifecycle stage, governing policy, and EOL floor without presenting that floor as a date.

Written by the indexing model from the issue text.

Description

Where. 12-writer-palmyra/01-palmyra-vision.ipynb, cell 0, the paragraph that begins "IDs, context window and output limit from the model card, read on 20 October 2026".

What is wrong. The notebook states no lifecycle fact for Palmyra Vision 7B: not the stage, not the lifecycle policy that governs it, not the earliest end-of-life date. Its card carries all three, and the earliest EOL date is about four and a half months away. The notebook in the same folder devotes a long paragraph to exactly these fields for X4 and X5, so a reader who has read 02 and comes to 01 is entitled to read the silence as "nothing to say here" rather than as "not written down".

Evidence. Model card read 7 November 2026 in its markdown form, https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-writer-palmyra-vision-7b.html, Model Details, verbatim:

+ **Model launch date:** Mar 26, 2026
+ **EOL no sooner than:** Mar 26, 2027
+ **Legacy period:** at least 6 months
+ **Model lifecycle policy:** [Model lifecycle (For Models Launched Prior to Sept 7 2026)](model-lifecycle-legacy.md)
+ **Model EOL date:** N/A
+ **Model lifecycle:** Active

Measured against the live service the same day, GetFoundationModel on writer.palmyra-vision-7b:

us-east-1 lifecycle= {'status': 'ACTIVE', 'startOfLifeTime': datetime.datetime(2026, 3, 20, 17, 0, tzinfo=tzlocal())}
us-west-2 lifecycle= {'status': 'ACTIVE', 'startOfLifeTime': datetime.datetime(2026, 3, 20, 17, 0, tzinfo=tzlocal())}

So card and service agree on Active / ACTIVE, and the model is governed by the legacy lifecycle policy (launched before 7 September 2026) rather than the current one — the same split 11-xai-grok/03 section 1 explains for Grok 4.7 against 4.6 and 4.3.

That this is the only family notebook without it, counting lifecycle mentions (EOL no sooner, Model lifecycle, model-lifecycle, Legacy period) per notebook on main at c3d55ff8:

6  ./12-writer-palmyra/02-palmyra-x4-x5-on-runtime.ipynb
5  ./13-amazon-nova/01-nova-ladder-and-vision.ipynb
5  ./08-moonshot-kimi/02-kimi-k3.ipynb
4  ./06-zai-glm/01-glm-family.ipynb
...
0  ./12-writer-palmyra/01-palmyra-vision.ipynb

Every NN-<provider>/ notebook carries at least one except this file and 06-zai-glm/02-glm-5-3.ipynb. The house style to match is in 02-palmyra-x4-x5-on-runtime.ipynb cell 0, which names the stage, the governing lifecycle page, the EOL date, and what the stage means for a reader's access and price.

Severity. Medium. Nothing a reader copies breaks, so it is not high. But "how long can I build on this" is one of the first questions a developer asks of a model, the card answers it, the sibling notebook answers it for the other two models in the same folder, and this file leaves the reader to go and find it — with the extra trap that Palmyra Vision runs under the pre-September-2026 policy, which the collection elsewhere treats as a material difference.

Proposed change. Add a short dated paragraph to cell 0, after the IDs-and-window paragraph. Figures below are mine from 7 November 2026; re-read the card and re-run GetFoundationModel before committing, because both move:

Palmyra Vision 7B is in the Active stage: its card reads Model lifecycle: Active with Model EOL date: N/A, and GetFoundationModel returned ACTIVE for writer.palmyra-vision-7b in us-east-1 and us-west-2 (card and service read 7 November 2026). It launched on 26 March 2026, so it falls under the lifecycle policy for models launched before 7 September 2026 rather than the current one, and its card puts EOL no sooner than at 26 March 2027 with a Legacy period of at least six months. Palmyra X4 and X5 are already in the Legacy stage with announced EOL dates, which 02-palmyra-x4-x5-on-runtime sets out.

One sentence of that is worth the care: EOL no sooner than is a floor and not a date, which 02 already says in so many words ("The EOL no sooner than field beside those dates is a floor rather than a date"). Keep that distinction here rather than writing 26 March 2027 as the EOL.

Dominant language
Jupyter Notebook
Stars
2
Forks
2
Avg merge
5h 36m
Merged PRs (30d)
372

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/sample-per-model-bedrock

All issues in aws-samples/sample-per-model-bedrock

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.