Asteria Investment Office JSON
Use this skill for Asteria tasks that require a schema-locked JSON object built from live portfolio data. The local payloads are context, not the source of truth.
Operating rules
- Read the prompt, all payload files, and the answer template first.
- Treat any stale snapshot or memo in the payload as advisory only.
- Use the live Asteria service as the book of record.
- If payload data and live data conflict, follow the live data and reflect that in any precedence field the template asks for.
- Return only the JSON object requested by the template. No prose, no markdown, no code fences.
- Match every required key, list order, and numeric precision exactly.
Live data map
See references/environment.md for the endpoint list and request notes.
Use the live service this way:
- Portfolio and credit tasks: read portfolios, holdings, bond universe, issuers, energy market notes, and policies.
- Correlation tasks: read index metadata, index level history, and policies.
- Allocation and committee tasks: read opportunity-set taxonomy, prior views, macro signals, and policies.
Decision workflow
- Identify the portfolio id, task family, required fields, and ordering rules from the template.
- Pull the live records needed for that task family.
- Reconcile the local memo against live data.
- Compute the requested output from the live records.
- Draft the JSON to the exact schema.
- Validate structure, ordering, and rounding before answering.
Credit and rotation tasks
When the task asks for a trade package, rotation, or candidate selection:
- Use current holdings, the live bond universe, issuer status, and the policy thresholds.
- Prefer candidates marked eligible in the live universe.
- Avoid watchlisted or otherwise flagged issuers unless the prompt explicitly asks for them or the policy allows them for the objective.
- Preserve the requested constraint envelope rather than chasing headline carry.
- Recompute any post-trade totals, HY share, duration, and exposure fields from the proposed trades plus current holdings.
- If the prompt asks for a client-facing pitch angle, align the theme to the dominant live macro signal, not the stale worksheet.
Correlation tasks
When the task asks for index correlations or diversification actions:
- Use the requested index ids from the prompt.
- Pull the full monthly level series for each index.
- Convert levels to monthly simple returns before computing correlations.
- Use Pearson correlation over the requested window.
- Sort pair ids alphabetically.
- Use the live correlation policy thresholds when flagging concentration and diversification candidates.
Allocation and committee tasks
When the task asks for active views or committee decisions:
- Pull the opportunity-set taxonomy, prior views, macro signals, and allocation policy.
- Keep the output rows in the order required by the request payload or template.
- Map signal scores to views with the live policy thresholds.
- Use the absolute signal score to set conviction.
- Set change relative to the prior quarter or prior view record.
- Choose rationale codes that match the dominant live driver, not a generic label.
- Keep any overlay or next-step field consistent with the same signal story.
Calculations
- Simple return =
level_t / level_(t-1) - 1
- Correlation = Pearson correlation of overlapping monthly simple returns
- Round only after the final calculation so intermediate values stay accurate
Policy use
If /api/policies is available, use it before finalizing:
- Credit policies give the live HY cap, duration band, issuer concentration limit, and required reduction target.
- Correlation policy gives the window and the concentration thresholds.
- Allocation policy gives the view and conviction score cutoffs.
Do not hard-code those numbers unless the task itself supplies them as authoritative.
Final check
Before responding, verify:
- The JSON matches the template exactly.
- No extra keys are present.
- Lists are sorted as required.
- Dates use the requested format.
- Numeric fields use the requested precision.
- The response contains only JSON.
1---2name: asteria-investment-office-json-63description: Generate strict JSON answers for Asteria Investment Office portfolio tasks by reconciling the local memo with the live shared environment. Use this whenever the prompt asks for credit trade packages, fixed-income rotations, correlation reviews, allocation views, committee memos, or any response built from current Asteria portfolio, holdings, bond, index, macro, or policy records, especially when the prompt mentions stale worksheets or a current book of record.4metadata:5 source: https://skillmd.com/skills/prism-shadow/asteria-investment-office-json-66---78# Asteria Investment Office JSON910Use this skill for Asteria tasks that require a schema-locked JSON object built from live portfolio data. The local payloads are context, not the source of truth.1112## Operating rules1314- Read the prompt, all payload files, and the answer template first.15- Treat any stale snapshot or memo in the payload as advisory only.16- Use the live Asteria service as the book of record.17- If payload data and live data conflict, follow the live data and reflect that in any precedence field the template asks for.18- Return only the JSON object requested by the template. No prose, no markdown, no code fences.19- Match every required key, list order, and numeric precision exactly.2021## Live data map2223See `references/environment.md` for the endpoint list and request notes.2425Use the live service this way:2627- Portfolio and credit tasks: read portfolios, holdings, bond universe, issuers, energy market notes, and policies.28- Correlation tasks: read index metadata, index level history, and policies.29- Allocation and committee tasks: read opportunity-set taxonomy, prior views, macro signals, and policies.3031## Decision workflow32331. Identify the portfolio id, task family, required fields, and ordering rules from the template.342. Pull the live records needed for that task family.353. Reconcile the local memo against live data.364. Compute the requested output from the live records.375. Draft the JSON to the exact schema.386. Validate structure, ordering, and rounding before answering.3940## Credit and rotation tasks4142When the task asks for a trade package, rotation, or candidate selection:4344- Use current holdings, the live bond universe, issuer status, and the policy thresholds.45- Prefer candidates marked eligible in the live universe.46- Avoid watchlisted or otherwise flagged issuers unless the prompt explicitly asks for them or the policy allows them for the objective.47- Preserve the requested constraint envelope rather than chasing headline carry.48- Recompute any post-trade totals, HY share, duration, and exposure fields from the proposed trades plus current holdings.49- If the prompt asks for a client-facing pitch angle, align the theme to the dominant live macro signal, not the stale worksheet.5051## Correlation tasks5253When the task asks for index correlations or diversification actions:5455- Use the requested index ids from the prompt.56- Pull the full monthly level series for each index.57- Convert levels to monthly simple returns before computing correlations.58- Use Pearson correlation over the requested window.59- Sort pair ids alphabetically.60- Use the live correlation policy thresholds when flagging concentration and diversification candidates.6162## Allocation and committee tasks6364When the task asks for active views or committee decisions:6566- Pull the opportunity-set taxonomy, prior views, macro signals, and allocation policy.67- Keep the output rows in the order required by the request payload or template.68- Map signal scores to views with the live policy thresholds.69- Use the absolute signal score to set conviction.70- Set change relative to the prior quarter or prior view record.71- Choose rationale codes that match the dominant live driver, not a generic label.72- Keep any overlay or next-step field consistent with the same signal story.7374## Calculations7576- Simple return = `level_t / level_(t-1) - 1`77- Correlation = Pearson correlation of overlapping monthly simple returns78- Round only after the final calculation so intermediate values stay accurate7980## Policy use8182If `/api/policies` is available, use it before finalizing:8384- Credit policies give the live HY cap, duration band, issuer concentration limit, and required reduction target.85- Correlation policy gives the window and the concentration thresholds.86- Allocation policy gives the view and conviction score cutoffs.8788Do not hard-code those numbers unless the task itself supplies them as authoritative.8990## Final check9192Before responding, verify:9394- The JSON matches the template exactly.95- No extra keys are present.96- Lists are sorted as required.97- Dates use the requested format.98- Numeric fields use the requested precision.99- The response contains only JSON.