Skip to content
Discussion options

You must be logged in to vote

What you have is "valid but lossy": collapsing the whole table into one content string is fine for summarization, but you lose the dept→queue mapping.

If your agent only needs to talk about contributors, it's OK. If it needs to filter ("what’s the queue for Physics?"), encode the table as a separate TOON array.

I'd keep the table as structure, not just prose. For example:

sections[1]:
  - id: 10
    title: Condo Department-level Contributor Highlight
    blurb: Here is a table...
    contributors[5]{department,queue}:
      Life & Environmental Science,dept.les
      Applied Math,dept.appliedmath
      Cognitive Science,dept.cogsci
      Center for Cellular and Biomolecular Machines,grp.c…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by johannschopplich
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants